This guide is designed for Enterprise customers. If you’re not on an Enterprise subscription, contact our sales team to learn more about Enterprise features.
What You’ll Set Up
Single Sign-On (SSO)
Secure authentication through your identity provider (Okta, Azure AD/Entra ID, or Google Workspace)
Directory Sync & Groups
Automatic user provisioning and bulk access management from your IDP
Organization Structure
Projects, teams, and workspace organization best practices
Role-Based Access Controls
Granular permissions at organization, project, and asset levels
Usage Controls
Credit limits, monitoring, and usage alerts across your organization
Event Streaming
Audit logs and compliance data streamed to your S3 bucket
Integration Governance
Control which third-party integrations your teams can use
API Key Management
Organization and project-level API keys for secure automation
Data Retention
Automatically manage data lifecycle and retention policies
User Level Authentication
Enable agents to use each user’s own credentials for integrations
Prerequisites
Required for setup:- An active Enterprise subscription with Relevance AI
- Organization Owner or Admin access in Relevance AI
- Access to your identity provider (Okta, Azure AD/Entra ID, or Google Workspace)
- Admin credentials for your identity provider
If you don’t have these prerequisites, contact your Relevance AI sales representative or reach out to support.
Recommended Setup Order
Follow these steps in order for the smoothest Enterprise onboarding experience. Each step builds on the previous one to create a secure, well-governed AI platform for your organization.Connect Single Sign-On (SSO)
Why this matters: SSO is the foundation of Enterprise security. It ensures all users authenticate through your identity provider, enabling centralized access control and compliance.What you’ll do:
- Configure SSO with your identity provider (Okta, Azure AD/Entra ID, or Google Workspace)
- Test SSO login flow
- Enforce SSO for all organization members
Enable Directory Sync & Groups
Why this matters: Directory Sync automatically provisions users and syncs groups from your identity provider, eliminating manual user management and enabling bulk access control.What you’ll do:View Directory Sync setup guide →
- Connect your identity provider directory to Relevance AI
- Configure which groups to sync
- Verify group synchronization
Feature Status: Directory Sync & RBAC Groups are in Beta with full rollout by November 20, 2025. Contact your sales representative to enable this feature.
Plan Your Organization & Project Structure
Why this matters: A well-planned organizational structure makes it easier to manage permissions, track usage, and scale your AI workforce as your team grows.What you’ll do:
- Decide how to organize projects (by team, department, or use case)
- Plan folder structure for agents and assets
- Determine project ownership and admin assignments
Configure Role-Based Access Controls (RBAC)
Why this matters: RBAC ensures users only have access to what they need, supporting security, compliance, and operational control.What you’ll do:
- Assign organization-level roles (Owner, Admin, Member, Viewer)
- Set project-level permissions (Admin, Editor, Member, Chat, Viewer)
- Configure asset-level access for sensitive agents and tools
- Assign groups to projects and assets (if using Directory Sync)
Set Usage Limits & Monitoring
Why this matters: Usage controls help you manage costs, prevent overuse, and ensure fair resource allocation across teams.What you’ll do:
- Set organization-wide credit limits
- Configure project-level usage caps
- Set up usage alerts and notifications
- Review usage dashboards
Connect S3 Bucket for Event Streaming (Optional)
Why this matters: Streaming events to your own S3 bucket provides audit logs, compliance data, and usage analytics for your security and data teams.What you’ll do:View event streaming setup guide →
- Create and configure an S3 bucket
- Set up IAM permissions
- Connect your bucket to Relevance AI
- Verify event streaming
Feature Status: S3 Event Streaming will be fully available by November 20, 2025, with self-serve setup by end of year. Contact your sales representative for early access.
Configure Integration Controls
Why this matters: Integration controls let you govern which third-party services your teams can connect, supporting security policies and compliance requirements.What you’ll do:
- Review available integration controls
- Set organization-level integration policies
- Configure project-level integration restrictions
Set Up API Key Management (Optional)
Why this matters: Organization and project-level API keys allow you to centrally manage credentials for integrations, ensuring consistent authentication across your teams and simplifying key rotation.What you’ll do:View API key management guide →
- Configure organization-level API keys for company-wide integrations
- Set project-level API keys to override organization defaults when needed
- Understand key precedence (project-level overrides organization-level)
If you set an API key at the organization level, all projects will use it unless a project-level key is specified. Project-level keys always take precedence over organization-level keys.
Configure Data Retention (Optional)
Why this matters: Data Retention policies help you meet compliance requirements, reduce security risks, and optimize storage by automatically deleting old data.What you’ll do:View Data Retention setup guide →
- Request Data Retention feature enablement from Relevance AI
- Set your organization’s retention period (in days)
- Configure automatic deletion policies for tool runs, conversations, and versions
- Understand what data is protected from deletion
Feature Status: Data Retention must be enabled by the Relevance AI team. Contact your sales representative to request this feature.
Enable User Level Authentication (Optional)
Why this matters: User Level Authentication allows each user to authenticate with their own credentials when using agents, ensuring privacy and proper access control across integrations.What you’ll do:
- Enable User Level Authentication on agent tools that use OAuth integrations
- Users will be prompted to connect their own accounts when using agents
- Credentials are saved and reused automatically for future runs
Feature Rollout Timeline
Some Enterprise features are being gradually rolled out. Here’s what to expect:| Feature | Status | Availability |
|---|---|---|
| SSO (Okta, Azure AD/Entra ID) | ✅ Available | Now |
| RBAC (Organization, Project, Asset) | ✅ Available | Now |
| Directory Sync & Groups | 🔄 Beta | Full rollout by Nov 20, 2025 |
| Integration Controls | ✅ Available | Now |
| Data Retention | ✅ Available | Contact sales to enable |
| S3 Event Streaming | 🔄 Beta | Full availability Nov 20, 2025; Self-serve by EOY |
| Organization & Project-level API Keys | ✅ Available | Now |
| Asset-level Authentication Controls | ✅ Available | Now |
| User Level Authentication | 🔄 Rolling out | Contact sales to enable |
If you have an Enterprise subscription but don’t have access to a feature marked as “Beta” or “Gradual rollout,” contact your sales representative to express interest and get early access.
Best Practices for Enterprise Deployment
- Security First
- Scale with Groups
- Plan Structure
- Access Control
- Governance
- Pilot & Monitor
Configure Security Before Inviting Users
Set up SSO and RBAC before inviting your entire organization. This ensures users have appropriate access from day one and prevents security gaps during onboarding.Initial security setupComplete SSO setup and test with a pilot group before enforcing it organization-wide. Configure organization and project-level roles thoughtfully, ensuring that sensitive resources have additional asset-level permissions.Multi-factor authenticationWork with your identity provider team to enable multi-factor authentication (MFA) for an additional security layer. This is especially important for Admin and Owner roles.The cost of shortcutsThe security foundation you build now will scale with your organization. Taking shortcuts during initial setup often leads to security remediation work later, which is more disruptive and time-consuming than getting it right from the start.Next Steps
Once you’ve completed the setup steps above, you’re ready to start building your AI workforce:Build Your First Agent
Create an AI agent to automate tasks and workflows
Create a Workforce
Build multi-agent teams for complex workflows
Start Using Chat
Interact with AI agents through conversational chat
Browse the Marketplace
Discover pre-built agents, tools, and templates
Add Knowledge
Connect your data sources to power your agents
Explore Integrations
Connect your favorite tools and services
Frequently asked questions (FAQs)
How long does Enterprise setup take?
How long does Enterprise setup take?
Most organizations complete the core setup (Steps 1-5) in 2-3 hours. The optional steps (Data Retention, S3 streaming, integration controls) add another 30-60 minutes. If you’re planning your organization structure carefully, allow additional time for that planning phase.
Can I skip steps in the recommended order?
Can I skip steps in the recommended order?
While you can technically skip steps, we strongly recommend following the order. SSO and Directory Sync should always come first, as they affect how users access the platform. Skipping these steps may require you to reconfigure access later, which can disrupt your users.
What if I don't have an identity provider?
What if I don't have an identity provider?
Enterprise features require an identity provider (Okta, Azure AD/Entra ID, or Google Workspace). If you don’t have one, you’ll need to set one up before using SSO and Directory Sync features. Most organizations already have an IDP for email and other services.
How do I get help during setup?
How do I get help during setup?
Enterprise customers have access to dedicated support. Contact your sales representative or reach out to our support team via your Slack channel or other support methods. We can also provide setup assistance for complex deployments.
What happens if I don't complete all setup steps?
What happens if I don't complete all setup steps?
You can use Relevance AI without completing all steps, but you won’t have full Enterprise security and governance capabilities. We recommend completing at least Steps 1-4 (SSO, Directory Sync, Organization Structure, and RBAC) for a secure deployment.
Do I need Directory Sync if I only have a small team?
Do I need Directory Sync if I only have a small team?
For teams under 20 users, Directory Sync is optional but still recommended. Manual user management works fine for small teams, but Directory Sync makes it easier to scale and ensures your access control stays in sync with your organization’s identity provider.
Can I use Relevance AI without SSO?
Can I use Relevance AI without SSO?
Yes, but it’s not recommended for Enterprise customers. SSO provides centralized access control, enhanced security, and is required for features like Directory Sync. For Enterprise deployments, SSO should be considered essential.
Need help? Enterprise customers have access to dedicated support channels. Contact your sales representative or reach out to our support team for assistance with your Enterprise setup.