> ## 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}/).

# Getting started with FedRAMP 20x Secure Configuration

> Recommended Perplexity Enterprise settings for a FedRAMP 20x-aligned secure configuration: SSO, SCIM, sharing, file, retention, and audit controls.

This article lists the Perplexity Enterprise settings that support a FedRAMP 20x-aligned secure configuration, for organization administrators at government agencies. Each recommendation names the control, why it matters, and where to find it.

> [!NOTE]
>
> Retention policies and audit logging are available to Enterprise organizations with 50 or more seats, or with at least one Enterprise Max seat.

## Before you start

<ul>
  <li>
    You need an organization administrator role, or a custom role with the relevant permissions. See [Introduction to organization admins](https://www.perplexity.ai/help-center/help-center/en/articles/12067853-introduction-to-organization-admins.md) and [User management for Enterprise organizations](https://www.perplexity.ai/help-center/help-center/en/articles/10352978-user-management-for-enterprise-organizations.md).
  </li>

  <li>
    For SSO and SCIM, you need administrator access to your agency's identity provider.
  </li>

  <li>
    If your organization is new to Perplexity Enterprise, complete the [Perplexity Enterprise onboarding guide](https://www.perplexity.ai/help-center/help-center/en/articles/12742827-perplexity-enterprise-onboarding-guide.md) first.
  </li>
</ul>

## Recommended configuration

For FedRAMP 20x-aligned secure configuration, Perplexity recommends centralizing identity through SSO, managing user lifecycle through your identity provider, restricting external sharing, applying file and retention controls, and enabling audit logging.

### Use Single Sign-On (SSO)

Perplexity recommends enabling and enforcing SSO for Enterprise organizations, and verifying your domains, so authentication is managed through your agency's identity provider. SSO helps centralize access control, support domain-based restrictions, and reduce reliance on standalone passwords. For setup steps, see [SSO Integration: Getting Started](https://www.perplexity.ai/help-center/help-center/en/articles/11200832-sso-integration-getting-started.md).

Go to **Organization Settings → [Identity](https://www.perplexity.ai/account/org/identity)**.

### Manage users through your identity provider

Where available, use SCIM to keep user access aligned with your agency directory. This helps automate onboarding, role assignment, and deprovisioning as users join, move, or leave the organization. See [Account Management for SSO](https://www.perplexity.ai/help-center/help-center/en/articles/11199947-account-management-for-sso.md), [SCIM-based user account management](https://www.perplexity.ai/help-center/help-center/en/articles/11652604-scim-based-user-account-management.md), and [Managing users and access control](https://www.perplexity.ai/help-center/help-center/en/articles/11187370-managing-users-and-access-control.md).

Go to **Organization Settings → [Identity](https://www.perplexity.ai/account/org/identity)**.

### Limit public sharing

Perplexity recommends disabling public sharing for sessions and Pages unless your agency has explicitly approved those use cases. Projects cannot be shared by public link. The **Allow public project sharing** toggle controls whether members can invite people outside your organization to Projects; turn it off to keep Projects organization-only. Project access is otherwise limited to invited members, organization access, and approved join requests. Keeping sharing organization-only helps reduce the risk of sensitive information being exposed outside the agency environment. The **Allow public session sharing**, **Allow public page sharing**, and **Allow public project sharing** settings are described in [Enterprise roles and permissions](https://www.perplexity.ai/help-center/help-center/en/articles/11187754-enterprise-roles-and-permissions.md).

Go to **Organization Settings → [Data and privacy](https://www.perplexity.ai/account/org/data-privacy)**.

### Restrict file actions

Perplexity recommends limiting members' ability to download files or attach files to sessions unless required for an approved workflow. These controls help reduce unnecessary movement of sensitive data and keep file handling under administrator oversight. The **Download files** and **Attach files to sessions** permissions are described in [Enterprise roles and permissions](https://www.perplexity.ai/help-center/help-center/en/articles/11187754-enterprise-roles-and-permissions.md).

Go to **Settings → Organization → [Roles & Permissions](https://www.perplexity.ai/account/org/roles-permissions)**.

### Use approved connectors only

Perplexity recommends enabling only the third-party connectors your agency has reviewed and approved. Connector settings let administrators control access to services such as Google Drive, OneDrive, SharePoint, Slack, Jira, GitHub, and other integrated applications, and set whether newly launched connectors are enabled by default. See [Enterprise roles and permissions](https://www.perplexity.ai/help-center/help-center/en/articles/11187754-enterprise-roles-and-permissions.md).

Go to **Organization Settings → [Connectors](https://www.perplexity.ai/account/org/connectors)**.

### Keep model providers enabled by default

Perplexity recommends keeping the standard Enterprise model provider configuration enabled unless your agency has a specific policy restriction. This preserves access to the Enterprise model set while still allowing administrators to align model availability with internal requirements. See [Data retention and privacy for Enterprise organizations](https://www.perplexity.ai/help-center/help-center/en/articles/11187708-data-retention-and-privacy-for-enterprise-organizations-and-users.md).

Go to **Organization Settings → [Data and privacy](https://www.perplexity.ai/account/org/data-privacy)**.

### Enable API access only when needed

Perplexity recommends enabling API access only for approved agency use cases, such as sanctioned development or integration workflows. Review API access before enabling it, and limit it to users or teams with a documented need. The **Perplexity API access** permission is described in [Enterprise roles and permissions](https://www.perplexity.ai/help-center/help-center/en/articles/11187754-enterprise-roles-and-permissions.md).

Go to **Settings → Organization → [Roles & Permissions](https://www.perplexity.ai/account/org/roles-permissions)**.

### Configure retention and history settings

Perplexity recommends configuring session retention to match your agency's records, privacy, and compliance requirements. Administrators can turn on **Enforce Incognito Mode** and set a retention period for sessions. For how retention is measured and what happens to sessions outside the retention period, see [Data Retention for Enterprise](https://www.perplexity.ai/help-center/help-center/en/articles/11652701-data-retention-for-enterprise.md).

Go to **Organization Settings → [Data and privacy](https://www.perplexity.ai/account/org/data-privacy)**.

### Enable audit logging

Perplexity recommends enabling audit logs for organizations that need activity monitoring and compliance evidence. Audit logs capture queries, file uploads, and organization settings changes, and are delivered to a webhook endpoint you configure. See [Audit Logs](https://www.perplexity.ai/help-center/help-center/en/articles/11652747-audit-logs.md) for setup and event types, and [Enterprise usage analytics](https://www.perplexity.ai/help-center/help-center/en/articles/11844346-enterprise-usage-analytics.md) for usage monitoring.

Go to **Organization Settings → [Data and privacy](https://www.perplexity.ai/account/org/data-privacy)**, then under **Audit Log Settings** select **Enable Audit Logging**.

## Security and compliance

Perplexity Enterprise and API Platform is FedRAMP Certified under the FedRAMP 20x program at the Low impact level (Class B), listed on the FedRAMP Marketplace as of February 1, 2026. For the authorization package, compliance certifications, sub-processor list, and data-handling documentation, visit the [Trust Center](https://trust.perplexity.ai/).

## Related articles

> **[Enterprise roles and permissions](https://www.perplexity.ai/help-center/help-center/en/articles/11187754-enterprise-roles-and-permissions.md)**

> **[Data Retention for Enterprise](https://www.perplexity.ai/help-center/help-center/en/articles/11652701-data-retention-for-enterprise.md)**

> **[Audit Logs](https://www.perplexity.ai/help-center/help-center/en/articles/11652747-audit-logs.md)**

> **[SSO Integration: Getting Started](https://www.perplexity.ai/help-center/help-center/en/articles/11200832-sso-integration-getting-started.md)**

> **[SCIM-based user account management](https://www.perplexity.ai/help-center/help-center/en/articles/11652604-scim-based-user-account-management.md)**

## Need more help?

Reach out to your account team or [contact us via **Help > Contact Support**](https://www.perplexity.ai/?support=true#settings/account). Visit the [Trust Center](https://trust.perplexity.ai/) for security and compliance documentation.


## Related topics

- [Enterprise admin hub](https://www.perplexity.ai/help-center/help-center/en/enterprise.md)
- [Perplexity Enterprise](https://www.perplexity.ai/help-center/help-center/en/collections/11312901-perplexity-enterprise.md)
- [एंटरप्राइज़ एडमिन हब](https://www.perplexity.ai/help-center/help-center/hi/enterprise.md)
- [Getting Started](https://www.perplexity.ai/help-center/help-center/en/collections/12702161-getting-started.md)
