Concepts
Permissions and scopes
Every agent connection carries scopes. You choose them when you approve an OAuth app, or when you create an API key.
| Scope | Allows | Typical use |
|---|---|---|
crm:read | Reading everything: search, records, pipeline, tasks, signals, change feed. | Reporting, research, answering questions. |
crm:suggest | Proposing changes with suggest_change. A person approves each one in Review, and approving runs it. | A cautious agent: it can do any write, but only through you. |
crm:write | Creating and updating records, deals, activity, tasks, signals and custom fields. Includes crm:suggest. | An agent you trust to keep the CRM up to date. |
crm:delete | Soft-deleting records. | Rarely needed by agents. |
OAuth apps get crm:read and crm:write by default when they register; you can approve less. API keys default to read and write too.
Tools you can't see
Tandem's MCP server builds the tool list for each connection from its scopes. A read-only agent never sees upsert_person or create_deal, so it can't try them. Tools that change workspace settings, approve suggestions or remove do-not-contact entries are for signed-in people only and never appear over MCP: see the "people only" tools in the tools reference.
Roles of people
People in a workspace are owners, admins or members. Owners and admins manage members, agents, API keys, billing, exports and erasure. Members work the CRM. An agent connected over OAuth acts on behalf of the person who approved it.