Integration Permissions
Which roles can connect, configure, and disconnect integrations, and how API key permissions work.
What this guide covers
This guide explains which user roles can manage integrations and how API key permissions control what data is accessible through the API.
Integration access by role
| Action | Owner | Admin | Dispatcher | Technician |
|---|---|---|---|---|
| Connect an integration | Yes | Yes | No | No |
| Configure integration settings | Yes | Yes | No | No |
| Disconnect an integration | Yes | Yes | No | No |
| View sync log | Yes | Yes | Yes | No |
| Trigger manual sync | Yes | Yes | No | No |
| Generate API keys | Yes | No | No | No |
| Set up webhooks | Yes | Yes | No | No |
| Connect personal calendar | Yes | Yes | Yes | Yes |
Screenshot: The integrations page as seen by a Dispatcher, showing sync log access but without Connect or Settings buttons.
API key permissions
Each API key has granular permissions per entity:
- Read -- can retrieve data via GET requests.
- Write -- can create and update data via POST and PATCH.
- Read + Write -- full access to the entity.
Set the minimum permissions needed for each integration.
Tip: Create a separate API key for each integration rather than sharing one key across multiple systems. This makes it easier to revoke access for a single integration without disrupting others.
Note: Only the workspace Owner can generate and manage API keys. Admins can manage integrations but cannot create API keys.
Related articles
Did this answer your question?