> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reachboost.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Choose what the app can access

> Access levels, the consent screen, and what an AI app can never do.

Permissions build on each other: outreach access includes read and write, resume access includes all three, and publish access includes all four. An app asks for the level it needs when it connects. The consent screen shows what it asks for, and you approve or deny that request as a whole.

## Access levels

| Access | What the app can do | Permission requested |
| - | - | - |
| **Read access** | Campaigns and their messages, leads, lead lists, tags, senders, webhooks, inbox conversations, workspace members and their invitations, and activity. | `mcp.read` |
| **Write access** | Change tags, lead lists, leads, draft campaigns and webhooks; edit or remove workspace members and invite or withdraw people. Changing members and invitations also needs the right role: a workspace admin, an agency admin, or an agency member listed on the client workspace. | `mcp.write` |
| **Outreach access** | Pause or finish a campaign, stop named leads, change a running campaign's limits and hours, rename or remove a sender. | `mcp.write_outreach` |
| **Resume outreach access** | Resume any paused campaign in the workspaces the app can reach, which makes your senders start sending again. | `mcp.outreach_start` |
| **Publish access** | Publish a draft campaign so your senders start sending it for the first time. Together with write access, the app can decide what a new campaign says and start it. | `mcp.campaign_publish` |

A write tool returns the record it changed, so a connection that can only write still sees what it touched. See [Tools](https://docs.reachboost.io/mcp/tools.md) for the access each tool needs.

## Limits that always apply

> [card] Additional permission required
>
> Lead email addresses, phone numbers and custom fields stay hidden unless your workspace turns them on.

> [card] Credits can be spent
>
> A connection can enrich a lead when you ask it to, which spends enrichment credits on the same terms as the app. Credits can also go without being asked for: adding or removing a tag on a lead can push that lead to a connected app, and if the app has enrich on push turned on and the lead still needs enriching, the push spends enrichment credits.

> [card] Never permitted
>
> No tool sends a message to a lead outside a campaign; a published or resumed campaign sends the steps it has.

## What read access covers

Read access covers your account, workspaces, workspace members including their names and email addresses, pending invitations including the names and email addresses of the people invited, senders, campaigns and the message text of each step, lead lists, leads, tags, webhooks including their URLs, activity statistics, the activity history of individual leads, and inbox conversations including message bodies and attachment links.

## Who can connect

You need an active ReachBoost workspace with a subscription or trial, and a user account that is not blocked.

## Disconnect an app

You can disconnect an app at any time. Access also ends when your subscription or trial ends.

> [card] [Manage connected apps](https://app.reachboost.io/integrations/mcp)
>
> AI apps you connected to ReachBoost through MCP, under **Integrations**, **MCP**. Disconnecting one revokes its access on its next request.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.