Sources & scopes
How connected data is divided up, and how that drives visibility.
Each connector divides its data into scopes — one per ingestion unit:
| Source | Scope |
|---|---|
| GitHub | a repository |
| Jira | a project |
| Linear | a team |
| Slack | a channel |
| Granola | a top-level folder |
Admins choose per scope whether it's ingested at all, and which visibility groups may see it (Settings → Sources). A scope with no groups is workspace-wide; a scope with groups is visible only to those groups and to admins.
Every record ingested from a scope carries its visibility. When an admin changes a scope's groups, every record from it is re-tagged, and API keys see the change immediately — a key with Selected groups → Engineering sees exactly the scopes assigned to Engineering, plus workspace-wide data.
Data written through the API isn't tied to a scope: it takes the writing key's visibility instead. See Data access.
The source allow-list on a key works at the source level (github, slack, api, …), independently of scopes.