# Access Guide

How the CloudFiles MCP server decides what a connection can reach: the user each connection acts as, who can create and end connections, and how production, sandbox and regions apply.

> Kind: Guide · Updated: Nov 4, 2026

Every request from an agent to the CloudFiles MCP server arrives on a connection. A connection belongs to one CloudFiles account and acts as one CloudFiles user: your account's system user for an MCP credential, or the person who signed in for an AI app. On every tool call, CloudFiles checks that the connection is still active, that the user can still act in the account, and that the user holds a license for the product the tool belongs to. It then carries out the action through your account's existing connections, such as your Salesforce org and connected storage libraries, the same way it does for CloudFiles Flow actions.

## Who can do what

| Action | Who can do it |
|---|---|
| Create, view and revoke MCP credentials | A CloudFiles admin |
| Connect an AI app such as Claude or ChatGPT | Any CloudFiles user in the account, except partner users |
| Disconnect an AI app | The person who connected it, from the app |
| End every app connection a person has made | A CloudFiles admin, by removing the person from the CloudFiles account |

## Access guides

1. **Who the Agent Acts As** — Learn which CloudFiles user each kind of connection acts as, what an agent can reach through your account's connections, which licenses apply, and what a person approves on the Connect with CloudFiles page.
2. **Revoke Access and Disconnect Apps** — End access for a service, an AI app or a person: revoke an MCP credential, replace a client secret, disconnect an app, or remove a person's access.
3. **Production, Sandbox and Regions** — Connect production and sandbox orgs separately, and use the MCP server for your CloudFiles account's data region.