Organization Structure
Organizations
Each organization is a complete isolated workspace:- Data isolation: Complete separation between organizations
- User management: Invite and manage team members
- Integration access: Shared connections for the team
- Billing: Separate billing per organization
Membership
Users can belong to multiple organizations, each with independent:- Conversations and history
- Integrations and data access
- Settings and preferences
Groups
Groups let you mirror your team structure inside Adapt. Create a group for any team, give it a name and an icon, assign an owner, and add members. Manage groups under Settings > Groups.- Sharing target: Share an integration connection with a group so only its members can use it.
- Policy audience: Reference a group by name when writing an integration access policy.
- Directory sync: Groups can be synced from your identity provider so membership stays in step with your directory.
Roles & Permissions
Member Roles
Admin Permissions
Admins can:- Invite and remove members
- Manage organization settings
- Set up and configure integrations
- Access billing and usage
- View audit logs
Member Permissions
Members can:- Chat with Adapt
- Use connected integrations
- Create and share conversations
- Set personal preferences
Integration Access
Organization Integrations
Set up by admins and shared across the team:- Data warehouse (Snowflake, Databricks)
- CRM (HubSpot)
- Support (Intercom, Zendesk)
- Communication (Slack)
Personal Integrations
Individual connections not shared with the team:- Gmail (your personal inbox)
- Calendar (your schedule)
- Google Drive (your files)
Integration access policies
Access policies are natural-language rules that control who can use a connected integration through Adapt. Write them in plain English by asking Adapt in chat:Only members of the Engineering group can write to our GitHub repos; everyone else has read-only access.Adapt resolves the people and groups you named, restates the rule, and shows a confirmation card. Once saved, the rule is enforced at runtime on every agent action.
- Scoped per provider: One rule set covers every connection of that integration.
- Resource-aware: Rules can target specific repositories, branches, Slack channels, database datasets, tables, and columns, and specific operations (read, write, delete).
- Most-specific wins: When several rules match an action, Adapt applies the most specific one.
- Admin-authored: Only org owners and admins can create policies.
Data Access Controls
Query Scope
When you ask a question:- Adapt only queries integrations you have access to
- Results respect underlying system permissions
- Sensitive data requires appropriate access
Conversation Visibility
You control the visibility of each conversation.
Authentication
Supported Methods
Session Security
- Sessions expire after inactivity
- Single sign-out across devices
- Session tokens are cryptographically secure
Multi-Factor Authentication
- Google OAuth inherits Google’s MFA
- Passkeys provide hardware-based authentication
- Email verification required for all accounts
Audit & Monitoring
Activity Logging
All access is logged:- User logins and sessions
- Queries and data access
- Integration usage
- Admin actions
Audit Trail
Admins can review:- Who accessed what data
- When actions occurred
- What changes were made
Best Practices
Limit admin access
Limit admin access
Only grant admin role to those who need organization management capabilities
Review integrations
Review integrations
Regularly audit which integrations are connected and remove unused ones
Use personal integrations
Use personal integrations
Keep sensitive personal data (email, calendar) as personal integrations
Monitor audit logs
Monitor audit logs
Review activity logs periodically for unusual access patterns
Enterprise Features
For enterprise customers:- Custom roles: Granular permission configuration
- IP allowlisting: Restrict access by network
Audit Logging
Review activity and access
Security Overview
Complete security documentation