> ## Documentation Index
> Fetch the complete documentation index at: https://www.perplexity.ai/help-center/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> This content comes from the official Perplexity Help Center. Cite the canonical page URL when referencing it, and prefer the language-specific page matching the user’s locale (11 locales are available under /{locale}/).
# Setting up SSO with Okta
> Step-by-step instructions for setting up Single Sign-On (SSO) integration between Okta and Perplexity Enterprise using SAML 2.0 authentication
**Before starting you will need:**
Administrative permissions in Okta Admin Console
Perplexity Enterprise organization and an active subscription with admin role
Verified organizational domain in Perplexity
Basic understanding of SAML concepts – Okta [has published a guide](https://www.apple.com/watch) covering the basic concepts
**Admin Role:** Must have administrator permissions in your Perplexity organization
**Enterprise Access:** Active Enterprise subscription (includes SSO capabilities)
## Okta
**Super Admin Access:** Administrative privileges in Okta Admin Console
**SAML Application Creation:** Ability to create custom SAML 2.0 integrations
**User Management Permissions:** Rights to assign applications to users/groups
**Provisioning Access:** Optional SCIM provisioning capabilities for automated user management
## Other requirements
Ensure firewall allows HTTPS traffic to Perplexity endpoints
No proxy interference with SAML authentication flows
Have at least one test user account in Okta directory, with a Perplexity Enterprise license
Consider creating dedicated SSO test group in Okta for initial testing
Consider having a backup admin account with non-SSO access for emergencies
## Configuring SSO in Perplexity
## Step 1: Navigate to Organization Settings
**Step 1**
Sign in to Perplexity Enterprise with your admin account
**Step 2**
Click on your organization in the bottom left corner
**Step 3**
Navigate to **[Identity](https://www.perplexity.ai/account/org/identity)** in Organization settings
[](../../assets/img/3e65a67504_Screenshot_2025-10-30_at_11_47_24.png)
**Step 4**
Click **Begin setup** in **SSO and SCIM**
## Step 2: Add and verify organizational domain
**Step 1**
Click **Add** next to the **Domains** option
**Step 2**
Enter your organization's domain (e.g., `yourcompany.com`) and click continue
**Step 3**
Copy the provided DNS TXT record
**Step 4**
Add the TXT record to your domain's DNS configuration
[](../../assets/img/05c9fe7763_image__2833_29.png)
Your domain will be automatically verified once we can detect that you added the record above. Normally, verification takes under a minute when adding a new record, but may take longer if you are updating an existing TXT record. If that’s the case, you can set a TTL of 60 seconds.
## Step 3: Select Identity Provider
**Step 1**
In Organization Settings, navigate to the **Identity Provider** section
**Step 2**
Click **Connect** to begin setup
**Step 3**
Select **Okta** from the available identity provider options
[](../../assets/img/d88ada0a7d_Screenshot_2025-10-30_at_11_51_37.png)
## Step 4: Record integration parameters
Perplexity will display the following required parameters for configuring Okta:
**IdP SSO URL** - The endpoint where Okta will post SAML responses
**Entity ID (Audience URI)** - Unique identifier for Perplexity service
**Required Attributes:**
Email address (primary identifier)
Full name (first name + last name)
Organization name (optional)
## Step 5: Prepare for IdP configuration
Keep the Perplexity configuration page open in a separate tab as you'll need to reference these values during Okta setup. Note down the exact values for easy copy-paste into Okta.
### **1. Access Okta Admin Console:**
[](../../assets/img/45a19e3020_Screenshot_2025-10-30_at_12_05_16.png)
**Step 1**
Navigate to your Okta Admin Console (typically `https://yourcompany.okta.com/admin`)
**Step 2**
Sign in with your Okta Super Admin account credentials
**Step 3**
From the **Admin Console** home page, navigate to **Applications** > **Applications**
### **2. Create SAML Integration**
We will present you with step-by-step documentation that will explain how to create a SAML integration for Perplexity in Okta. Read it carefully and follow every step.
**Step 1**
Click **Create App Integration** button
**Step 2**
Select **SAML 2.0** as the sign-in method
**Step 3**
Click **Next** to proceed to app configuration
### **3. Configure General Settings**
[](../../assets/img/1e6f9aac5d_Screenshot_2025-10-30_at_12_07_07.png)
**Step 1**
**App name:** Enter "Perplexity Enterprise" or other descriptive name
**Step 2**
**App logo:** Upload Perplexity logo (optional but recommended for user recognition)
**Step 3**
**App visibility:** Check **"Do not display application icon to users"** if you prefer icon-less experience
**Step 4**
Click **Next** to proceed to SAML configuration
### **4. Configure SAML Settings**
[](../../assets/img/662add8424_Screenshot_2025-10-30_at_12_10_21.png)
Enter the Perplexity parameters you recorded earlier:
**Single Sign-On URL Configuration:**
**Single sign-on URL:** Enter the **ACS URL/IdP SSO URL** from Perplexity configuration page
**Use this for Recipient URL and Destination URL:** Check this box
**Audience URI Configuration:**
**Audience URI (SP Entity ID):** Enter the **Entity ID** from Perplexity configuration page. Ensure this matches exactly with the value from Perplexity
**Additional SAML Configuration**
**Default Relay State:** Leave blank unless specified by Perplexity support
**Name ID format:** Select **EmailAddress**
**Application username:** Select **Email**
**Update application username on:** Select **Create and update**
### **5. Configure Attribute Statements**
[](../../assets/img/6e11695690_Screenshot_2025-10-30_at_12_11_38.png)
Map the following Okta attributes to Perplexity requirements:
**Attribute Name**
**Name Format**
**Value**
email
Basic
user.email
firstName
Basic
user.firstName
lastName
Basic
user.lastName
organization
Basic
user.organization (or user.department)
In the **Attribute Statements** section, click **Add Another**
Enter **email** as Name, leave Name format as **Basic**, enter **user.email** as Value
Add **firstName** attribute with **user.firstName** value
Add **lastName** attribute with **user.lastName** value
Add **organization** attribute with **user.organization** or **user.department** value
### **6: Configure Group Attribute Statements (Optional)**
[](../../assets/img/341b39dfc7_Screenshot_2025-10-30_at_12_13_28.png)
For advanced group-based access control, fill out the **Group Attribute Statements** section:
**Name:** groups
**Name format:** Basic
**Filter:** Select relevant filter (e.g., "Starts with" and enter "Perplexity\_")
### **7. Optional: Preview the SAML assertion**
[](../../assets/img/10a0a95b4f_Screenshot_2025-10-30_at_12_14_06.png)
Click **Preview the SAML Assertion** to see the XML that will be used in the assertion, and to verify the information you entered.
[](../../assets/img/a36eaa2493_Screenshot_2025-10-30_at_12_14_33.png)
### **8. Feedback and Finish**
You can provide to Okta more information about the SAML app. This section is optional.
### **9. Assign Users and Groups**
Once you have created the Perplexity app, it’s time to assign users and/or groups to it.
[](../../assets/img/9b8d4bb536_Screenshot_2025-10-30_at_12_17_14.png)
**Step 1**
Navigate to the **Assignments** tab in your newly created Perplexity app
**Step 2**
Click **Assign** > **Assign to People** for individual user assignment
**Step 3**
Or click **Assign** > **Assign to Groups** for group-based assignment
*It’s a good idea to create two groups (e.g., PPLX\_Admin and PPLX\_Members) before this step, and add users to these groups. You can then assign access to those groups in the Perplexity app in Okta.*\
[](../../assets/img/3299b143ce_Screenshot_2025-10-30_at_12_17_30.png)
**Step 4**
For initial testing, you can assign only your test users or a test group
**Step 5**
Click **Save and Go Back** after making assignments
[](../../assets/img/90d9ea87c6_Screenshot_2025-10-30_at_12_17_57.png)
\
### **10. Optional: Configure Automated Provisioning (SCIM)**
For automated user provisioning and deprovisioning:
**Step 1**
Navigate to the **Provisioning** tab
**Step 2**
Click **Configure API Integration**
**Step 3**
Check **Enable API integration**
**Step 4**
Follow the steps you’ll find in [this article](https://www.perplexity.ai/help-center/help-center/en/articles/11652604-scim-based-user-account-management.md), and configure provisioning features as needed.
## Step 5: Testing and verification
**Step 1**
**Logout** from your current Perplexity session completely
**Step 2**
**Clear browser cache and cookies** to ensure clean testing environment, or use an Incognito browser window
**Step 3**
**Close all browser tabs** related to Perplexity
**Step 4**
Navigate to Perplexity sign-in, and **enter email address** from verified domain (e.g., `testuser@yourcompany.com`)
**Step 5**
**Verify that you’re redirected** to Okta authentication page with your organization branding
**Step 6**
**Complete Okta authentication** using test account credentials and any required MFA
**Step 7**
**Verify that you’re successfully redirected** back to the Perplexity Enterprise dashboard
Currently, Perplexity does not support Identity Provider (IdP) initiated sessions.
However, there is a workaround: organizations can simulate IdP-initiated sessions by setting the URL target of their IdP's Perplexity tile to an organization-specific URL that initiates the SSO flow. If you need this org-specific URL, please get in touch.
## Troubleshooting common issues
## **SAML authentication failing**
**Symptoms:** Users redirected to error page after Okta authentication
**Solutions:**
Verify ACS URL and Entity ID are correctly entered in Okta SAML settings
Check that attribute mapping includes required email, firstName, and lastName fields
Ensure Name ID format is set to "EmailAddress" in Okta
Validate Okta certificate hasn't expired
Review SAML response in browser developer tools for specific errors
## **Attribute mapping errors**
**Symptoms:** User information not displaying correctly in Perplexity
**Solutions:**
Review Okta attribute statements configuration
Ensure all required attributes (email, firstName, lastName) are mapped correctly
Verify test user has necessary information populated in Okta profile
Check attribute names match exactly between Okta and Perplexity requirements
## **Invalid domain error**
**Symptoms:** "Domain not verified" message during login
**Solutions:**
Confirm DNS TXT record is properly configured in domain DNS settings
Allow 24-48 hours for DNS propagation globally
Use DNS lookup tools to verify TXT record visibility from multiple locations
Contact domain administrator if DNS changes are restricted