When CTD accesses your workspace (via domain-wide delegation on Google Workspace, or the CTD Connector app on Microsoft 365), you choose exactly how much access to grant. Access is split into four independent permissions. Here is what each one does, with a detailed guide for every choice:

Read access

Controls how much of your team’s email CTD can see. Two levels: metadata-only (participants and subject lines, with subjects stored encrypted) or read-only (message bodies fetched in real time when a user opens a message, never stored, plus contact details parsed from signatures).

Read access in detail →

Send access

Lets users send ghost emails from their own address in one click. CTD never sends anything automatically: every send is an explicit user action, whether in the app, via the API, or via MCP. Highly recommended, as ghost emails are one of CTD’s most used features.

Send access in detail →

Contacts access

Read-only sync of your team’s saved Google or Outlook contacts. Deliberately saved contacts join the relationship graph and show up as a scoring signal in Relationship Insights.

Contacts access in detail →

Calendar access

Read-only sync of your team’s calendars and events. Unlocks meeting prep with warm paths to every participant, per-relationship meeting history, more accurate scoring, and a meeting log on every contact.

Calendar access in detail →

Note: every permission here is read-only except Send, and even with read-only email access CTD never stores email bodies: they are fetched on demand and displayed in the app only. All permissions can be changed or revoked at any time.

Setting up the integration

During setup you combine your chosen read level with the optional Send, Contacts, and Calendar permissions into one list of OAuth scopes: