Manage agent scopes, grants, and credentials

An Agent Connection must pass three independent checks on every request:

1. A scope permits the capability, such as reading or writing tasks.
2. A project grant permits the target project, unless the connection is explicitly all-project.
3. The authorizing user's current ACL permits the same operation.

Grant the minimum useful combination. Reading tasks does not imply changing them. Context, Notes, documents, Focus, and time use separate scopes. Destructive operations such as archive remain visibly marked and permanent deletion is not exposed through MCP.

Selected-project access is the recommended default. All-project access is appropriate only when a trusted connection must operate across the complete workspace ledger. A newly created project is not silently exposed to an unrelated selected-project connection.

Credentials use a client ID and one-time client secret to obtain short-lived access tokens. Store them only in the agent host's approved secret configuration. Do not commit, print, paste, or pass them in shell arguments. Changing scopes or grants applies to subsequent calls without rotating the secret because ToDoddle reloads authorization on every request.

Rotate the secret when it is exposed or when custody changes. Update the host configuration and restart it, then verify a read. Disable or delete the connection to stop new tokens and calls. Also review the authorizing user's access when that person changes teams or leaves.

Quarterly, review connection labels, owners, last use, scopes, and project grants. Remove capabilities that no longer support an active workflow.