Authorization

Understand how Pivot handles authorization for integrations using roles and space-level access.

Integration Access Model

Each integration functions like a special type of user. While it does not appear in the standard Members list of a space, it is visible under Space Settings > Integrations.

This allows integrations to operate independently of member visibility while still being subject to role-based permissions.

Role Assignment

When you share a space with an integration, you assign it a role, just as you would for a team member. Roles define what the integration can access or perform within the space. Common examples include:

• Reader – View-only access.
• Admin – Full control over the space, including content and members.

You can assign different roles to the same integration across different spaces, depending on its function.

Organization-Level Access

Integrations can be granted organization-level permissions as needed. These determine the scope of what an integration can do across the platform:

• None – No org-wide visibility or control.
• Reader – Can access org-level data and read-only endpoints.
• Admin – Can perform administrative actions across the organization.

Fine-Grained Access Control

When creating or editing an integration, you define its access in detail:

• Select whether it has organization-level permissions.
• Choose which specific spaces or blocks it can access or modify.
• Define its capabilities, such as creating content, posting messages, or triggering actions.

This model ensures integrations are restricted to exactly what they need to perform.