Skip to main content
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.
Welcome to Relevance AI for Enterprise! This guide will walk you through the recommended setup process to get your organization up and running with enterprise-grade security, governance, and collaboration features. Enterprise features in Relevance AI provide your organization with advanced security controls, bulk user management, compliance capabilities, and granular access controls across your AI workforce.

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

Prerequisites

Before you begin, ensure you have all of these prerequisites. Missing any of these may prevent you from completing the setup process.
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.

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
Time required: 30-45 minutesView SSO setup guide →

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:
  • Connect your identity provider directory to Relevance AI
  • Configure which groups to sync
  • Verify group synchronization
Time required: 20-30 minutes
Feature Status: Directory Sync & RBAC Groups are in Beta with full rollout by November 20, 2025. Contact your sales representative to enable this feature.
View Directory Sync setup guide →

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
Time required: 15-30 minutes (planning)View organization structure best practices →

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)
Time required: 30-60 minutesView RBAC configuration guide →

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
Time required: 15-20 minutesView usage limits setup guide →

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:
  • Create and configure an S3 bucket
  • Set up IAM permissions
  • Connect your bucket to Relevance AI
  • Verify event streaming
Time required: 20-30 minutes
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.
View event streaming setup guide →

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
Time required: 15-20 minutesView integration controls guide →

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:
  • 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)
Time required: 10-15 minutes
Feature Status: Organization and project-level API keys are gradually being rolled out to Enterprise customers. Contact your sales representative to enable this feature.
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.
View API key management guide →

Feature Rollout Timeline

Some Enterprise features are being gradually rolled out. Here’s what to expect:
FeatureStatusAvailability
SSO (Okta, Azure AD/Entra ID)✅ AvailableNow
RBAC (Organization, Project, Asset)✅ AvailableNow
Directory Sync & Groups🔄 BetaFull rollout by Nov 20, 2025
Integration Controls🔄 Gradual rolloutRolling out to Enterprise customers
S3 Event Streaming🔄 BetaFull availability Nov 20, 2025; Self-serve by EOY
Organization & Project-level API Keys🔄 Gradual rolloutRolling out to Enterprise customers
Asset-level Authentication Controls✅ AvailableNow
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:

Frequently asked questions (FAQs)

Most organizations complete the core setup (Steps 1-5) in 2-3 hours. The optional steps (S3 streaming, integration controls) add another 30-60 minutes. If you’re planning your organization structure carefully, allow additional time for that planning phase.
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.
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.
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.
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.
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.