> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/fundamentals/faq/autorabit-platform-user-definitions.md).

# General User Definitions

{% hint style="info" %}
**ARM-Specific User Definitions**: The information below is generalized across the entire AutoRABIT suite of products. For information specific to ARM, please refer to the ARM User Definitions page [here](https://knowledgebase.autorabit.com/~/revisions/r1tfuUId2G5l58MjsNr3/product-guides/arm/arm-administration/user-management/arm-user-definitions). 
{% endhint %}

**Standard User**

A Standard User is an individual authorized by the Customer to log in to and fully utilize AutoRABIT’s subscribed products. Standard Users have access to all product functionalities, including the Web UI, IDE plugins, APIs, and other interfaces. 

Platform Owners/Admins are included in the Standard User class, ensuring administrative rights without affecting licensing terms. 

**Platform Integration User** 

A Platform Integration User is an individual authorized by the Customer to perform actions that trigger the execution of AutoRABIT products (directly or indirectly).  

This includes, but is not limited to: 

* Analyzing reports or data from AutoRABIT to identify and resolve code quality, security, compliance, or system performance issues. 
* Agents, bots, or systems executing actions via AutoRABIT to automate testing, deployments, or compliance checks. 
* Using AutoRABIT IDE plugins 
* Triggering AutoRABIT APIs 
* Directly changing Salesforce org configurations 
* Committing changes to a source code repository 

**Key Points:** 

* Automation (e.g., bots, agents) utilizing AutoRABIT for testing, deployment, or monitoring must be licensed appropriately. 
* Any person who commits code to a Source Code Management (SCM) system, where the commit directly or indirectly triggers a job in AutoRABIT, requires a Platform Integration License. 
* If a service account is used to trigger automation or integrate with AutoRABIT, the person or team responsible for the actual code commit must still hold a Platform Integration License. This ensures that each individual whose actions contribute to triggering AutoRABIT processes is appropriately licensed. 
* Any code commits triggering AutoRABIT jobs, directly or indirectly, manual or automated**,** count toward Platform Integration Licenses. 

Example: In Git, multiple commits pushed simultaneously are counted individually toward user licensing. 

Platform Integration Users are included in licensing with view-only permissions. 

**Additional Notes:** 

* The number of licensed users represents the total unique users of the products throughout the Subscription Term.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledgebase.autorabit.com/fundamentals/faq/autorabit-platform-user-definitions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.