Corvio · OAuth Scopes
Corvio OAuth Scopes
OAuth 2.0
searched
Corvio publishes 5 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Corvio API on a user’s behalf.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
CompanyArtificial IntelligenceNotesKnowledge ManagementWorkspaceAI AgentsMCPDeveloper APICLI
Scopes: 5
Flows:
Method: searched
Scopes (5)
| Scope | Description | Flows |
|---|---|---|
| questions:write | Required, with documents:write and document edit authority, for question runs that write documents (api.md). | |
| documents:write | Document write capability (api.md). | |
| comments:read | Remote MCP comment list via explicit OAuth scope (api.md). | |
| comments:write | Remote MCP comment create/reply/status and explicit change_summary discussion comments (api.md). | |
| admin_content:read | Admin CLI; "Exact Run content requires an explicit admin_content:read re-authorization." (https://corvio.ai/developers/admin-cli) |
📄 Provider scope reference: https://corvio.ai/developers/skills/corvio-operate-workspace/references/api.md
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.