> 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/vault/getting-started/control-access-to-the-salesforce-organization.md).
# Controlling Access to the Salesforce Org
AutoRABIT Vault allows administrators to restrict user access to specific Salesforce orgs registered within the account. Based on access permissions, users can perform AutoRABIT Vault operations such as **backup**, **restore**, **replication**, **comparison**, and **archival** on authorized Salesforce orgs only.
## Org Access Control Overview
The **Enable Org. Access Control** toggle on the **Manage Users** page is **enabled by default**. This setting grants the administrator the ability to define which users can access specific Salesforce orgs.
If this toggle is **disabled**, all users in the AutoRABIT Vault account will have **unrestricted access** to all registered Salesforce orgs.
***
## When "Enable Org. Access Control" Is Turned **On**
1. On the **Add User** screen, the **Salesforce Orgs** field becomes active.
2. The administrator must select one or more Salesforce orgs for the new user.
3. Users will have **access only to the Salesforce orgs explicitly granted** by the administrator.
4. Users are limited to performing AutoRABIT Vault operations within those assigned orgs.
***
## When "Enable Org. Access Control" Is Turned **Off**
1. All users in the AutoRABIT Vault account can access **all registered Salesforce orgs**.
2. Users can perform AutoRABIT Vault operations on **any org**, regardless of who registered it.
3. The **Salesforce Orgs List** will display **every org** currently registered in AutoRABIT Vault for all users.
---
# 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/vault/getting-started/control-access-to-the-salesforce-organization.md?ask=&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.
