> 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/product-guides/arm/getting-started-with-arm/understanding-arm/who-can-use-arm.md).

# Who can use ARM?

<table><thead><tr><th width="212.5">Users</th><th>Description</th></tr></thead><tbody><tr><td>Salesforce Administrators</td><td>Salesforce Administrators who want a faster, more powerful alternative to changesets that is easy to use and helps them quickly move changes without the command line</td></tr><tr><td>Salesforce Developers</td><td>Salesforce Developers looking for a tool that enables them to adopt modern development practices such as version control, continuous integration, and automated dependency analysis, while removing the need for the manual XML editing of Ant-based development</td></tr><tr><td>Release Managers</td><td>Release Managers and Technical Architects who want to improve deployment velocity, facilitate team collaboration, and deliver features to their end users quickly and reliable</td></tr><tr><td>Consultants and Implementation Partners</td><td>Consultants and Implementation Partners who want a way to build, track, and manage changes across multiple clients and organizations and provide detailed reports of their project progress.</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/arm/getting-started-with-arm/understanding-arm/who-can-use-arm.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.