Key capabilities
- Centralized management: Admin setup and approval for organization-wide connections
- Role-based access controls: Enforce scoped, least-privilege permissions
- Visibility and audit tracking: Track which apps use which services
- Bring your own OAuth (Enterprise only): Use organization-owned OAuth clients with custom scopes
- Per-app consent and easy revocation
How it works
Security and governance
- Scoped access with least-privilege permissions
- Credentials and tokens managed by the platform, not individual apps
- Centralized revocation and rotation without code changes
Setup and management
Enable new connectors
Configure the connector
Enable the connector using default configuration, or (Enterprise only) create an OAuth connector using custom configuration (for example, Drive scopes
.../auth/drive.file, .../auth/drive.install).Configure RBAC
- After enabling a connector, select Manage
- Grant access to a specific group
Modify connectors
- After enabling a connector, select Manage
- Deleting a connector removes connections for all builders in the organization
- Edit the scopes of a custom connector as needed
Plan controls
| Feature | Teams | Enterprise |
|---|---|---|
| Enable organization connectors | ✓ | ✓ |
| Create custom OAuth clients | — | ✓ |
| Set access controls on API keys | — | ✓ |
On Teams, API keys are available to all Members and Admins. Enterprise plans support access controls for API keys.
What’s next
Connectors for Organizations is expanding to support:- Webhook events for event-driven workflows
- Deeper admin experience with permissions, assignments, and analytics
Related documentation
- Connectors overview — Learn about all integration types
- Warehouse Connectors — Connect to BigQuery, Databricks, and Snowflake