DOCS · V1 · ATTIO
Attio OAuth scopes.
Scopes Foyai requests at install
The exact set, with what each is used for:
Scope
Used for
record_permission:read-writeRead deals, companies and people to build and update rooms. Write the foyai fields on deals and companies, and add identified buyers as People.
object_configuration:read-writeCreate the Foyai rooms object (
foyai_room) and the foyai_* fields on deals and companies, and read your configuration so setup and Re-sync only add what is missing.note:read-writeRead call notes when drafting a room. Write the "Foyai room activity" note for each buyer visit, and an AI intelligence note when a seller chooses to sync one.
task:read-writeCreate and update the action-plan tasks a seller sends to Attio, and keep their deadlines and completion in sync.
user_management:readMatch Attio workspace members to foyai users. Read-only: foyai cannot add, remove or change members.
webhook:read-writeSubscribe to changes on deals, companies, notes, tasks and call recordings, so rooms stay current. The full event list is on What foyai writes to Attio.
meeting:readRead meetings, so foyai can find the calls behind a deal and draft rooms from their transcripts.
call_recording:readRead call recording transcripts to draft rooms.
What Foyai does not request
- No access to lists, list entries, or comments. foyai doesn't request those scopes.
- No write access to meetings or call recordings. Those scopes are read-only.
- No write access to workspace members. foyai can see who is in the workspace, but cannot change it.
- No access to other workspaces. Installs are workspace-scoped.
Adding or changing scopes
If your workspace's Attio connection was made before a scope change, foyai prompts you to reconnect Attio. Attio's consent screen lists the requested scopes again before an admin approves, so foyai's access never grows without that approval.