Permissions & Integrations

Your board can't take on real work until it has access to real systems. Here's how to grant access — and how the scope model keeps it controlled.

How Scopes Work

agenté uses a principle of least privilege. When you connect an integration, you grant specific scopes — narrow permissions that define exactly what the board can and cannot do. Read-only access is separate from write access. Send authority is separate from delete authority. Nothing is granted by default.

Example: connecting Gmail with a read scope lets the board triage your inbox. It can see, sort, and draft — but it can't send until you explicitly grant the send scope. You escalate permissions deliberately, never accidentally.

Scopes can be revoked at any time. Disconnect an integration or narrow a scope and the board's access changes immediately.

Email

Connect Gmail or Outlook to let the board triage, prioritize, and draft responses.

• Read — the board sees your inbox and sorts it.
• Draft — the board composes suggested responses (saved as drafts, never sent).
• Send — the board can send approved responses. Grant this only after you've reviewed enough drafts to trust the voice.

Calendar

Connect Google Calendar or Outlook Calendar so the board knows your schedule, can book meetings, and can flag conflicts.

• Read — the board factors your availability into planning and briefings.
• Manage — the board can create, modify, and cancel events on your behalf.

Documents

Connect Google Drive, OneDrive, or Dropbox so the board can reference and generate documents.

• Read — the board pulls from your files when it needs context.
• Write — the board creates new documents (reports, drafts, summaries) in designated folders.

Financial Systems

Connect QuickBooks, Xero, or your accounting platform so the CFO seat can pull real numbers.

• Read — the board accesses financial reports and transactions for analysis.
• Write — limited and explicit. The board can categorize transactions or generate reports, but payments and transfers require your approval.

CRM

Connect your CRM (Salesforce, HubSpot, or agenté's built-in on Executive tier and above) so the CRO seat can manage pipeline.

• Read — the board tracks deals and customer history.
• Write — the board updates records, logs interactions, and advances pipeline stages.

Graduated Access

Permissions work like autonomy — start narrow, expand as trust builds. Day one, grant read access broadly and write access narrowly. Over the first week, widen scopes as you see the board's work quality. You can always pull back.

What's Next

• Security — how data isolation, encryption, and audit logs protect everything above.
• Uploading Documents — feed the knowledge base before the intake exam.