Authentication
Establish who the developer and user are before granting access. Identity is separate from the permission to perform an action.
YOUR SOFTWARE.
THE USER’S WORLD.
Connect an application to the tools, services and context the user allows. Permission belongs in the flow, from connection to execution.
PERMISSION
IN THE PATH.
Conceptual architecture. Provider names, supported scopes and execution contracts are not asserted here.
A CONNECTION
WITH BOUNDARIES.
Permission
Make the purpose of access understandable. The user chooses whether to grant it.
Scope
Bound access to the capability and context needed. Production scope names are not yet documented.
Connection
Represent the relationship to an authorized service, including its state and availability.
Execution
Check permission at the moment a tool or service is used. Surface results, errors and required approvals.
User control
Give users visibility into access and a way to disconnect or withdraw permission.
START WITH
THE USER.
Design the permission experience before the integration: what is needed, why it is needed and what the user can change.
No provider catalog or production connector API is documented on this Site. Use the concept guide to frame the flow, then verify the live contract before implementation.