Connecting accounts
When you connect an account, you grant the platform permission to act on your behalf at that service. The service asks you to approve a set of scopes (permissions); those scopes are locked in for that connection.
What you’re granting
Scopes determine what the platform can do at each service. You see them during the approval step.
| Provider | Scopes requested | What they cover |
|---|---|---|
| GitHub | repo, read:user, workflow | Read and write repos; read your profile; trigger Actions |
| drive.readonly, calendar.readonly | Read Drive files; read Calendar events | |
| Notion | read_content, update_content | Read and edit pages and databases |
| Linear | read, write | Read and create/update issues |
Gotchas
- Scopes are fixed when you connect. If a feature later needs an additional permission, disconnect and reconnect to grant the updated scope set.
- Google and Microsoft tokens expire after months of inactivity. If you see auth errors, disconnect and reconnect to get a fresh token.
- Each project gets its own connection. One project cannot use another project’s connected account — connect the account again in each project where you need it.
- If a connector prompts for new permissions after an update, disconnect and reconnect to grant them.