Permissions, identity, and attribution
Learn how OAuth scopes, team membership, collection access, and agent session identity constrain actions.
Last updated
An agent authorization is never a separate superuser. It belongs to one Quire user, one team, one OAuth client, and one MCP session.
Approval and scopes
The browser approval screen shows the requesting client, team, and scopes. Quire currently uses read, search, and write capabilities represented by docs:read, docs:search, and docs:write. Approve only the capabilities needed for the workflow.
Team membership and collection visibility remain authoritative after approval. If the member loses access to a collection, the agent loses it too. Ending team membership invalidates the useful authorization boundary.
Visible attribution
Agent changes identify the agent client and the person who authorized it. History, presence, comments, analytics, and webhook actors distinguish agent activity from human and system activity. Agent session IDs support traceability across operations.
Revoke access
Review active agent sessions from the Security page. Revoke a session you no longer recognize or need. The client must complete OAuth approval again before it can act.
Treat an approved agent like a collaborator operating with your access. Review its instructions, limit scopes, and supervise workflows that can move, delete, or broadly rewrite content.