Enterprise-managed authorization (EMA) , also known as Cross App Access (XAA), lets admins control how users authorize Claude to access the Lucid MCP server. Instead of each user signing in and authorizing access individually, MCP authorizations are handled through your identity provider (IdP), such as Okta, or through Claude-issued Managed Authorization. Once configured, the Lucid MCP server is automatically available across your organization.
Plan availability: Team and Enterprise.
Enterprise-managed authorization (EMA) options
You have two options when setting up Enterprise-managed authorization:
Refer to the sections below for details on each experience.
Set up enterprise-managed authorization through Claude
Before going through these steps, you need complete the following prerequisites:
Enable enterprise-managed authorization in the Lucid admin panel
To enable enterprise-managed authorization in the Lucid admin panel, follow these steps:
- Select Admin from the menu on the left side of the Lucid Home Page.
- Click App integration from the left side of the admin panel.
- Select General from the options that appear.
- Click Settings on the SAML tile.
- Enter your domain name under “Lucid sign-in URL”.
- Click Set up under "Enterprise-managed authorization”.
- Enter the Issuer URL you copied in the last section.
- Click Save changes.
After completing these steps, you need to test and enable managed authorization in the Claude Admin console. For more information about how to do this, check out this documentation from Claude.
Note: We work hard to ensure the information in the Lucid Help Center is up-to-date. However, the third-party resources linked in this section are not owned by Lucid and may change without notice. If you notice that this information is outdated, please let us know in the feedback survey linked at the bottom of this article.
Set up enterprise-managed authorization through Okta
Enterprise-managed authorization with Okta is enabled for Enterprise accounts using Okta SAML SSO. If you haven’t set up SAML in Lucid, refer to our Enable Okta SAML and SCIM in Lucid article.
Before configuring in Lucid, you’ll need to follow Okta's guide for setting up enterprise-managed authorization. Once you’ve done that, follow the steps below from your Lucid account.
- Log in to Lucid.
- Select Admin from the navigation menu on the left side.
- Click App integration from the navigation menu.
- Select General from the dropdown menu options.
- Click Settings on the SAML tile.
- Click Set up under "Enterprise-managed authorization”.
- Enter your Trusted issuer URL from Okta.
- Example: https://my-organization.okta.com
- Ensure your URL does not include a trailing slash.
- Click Save changes.
After completing these steps, you need to link the Lucid MCP to Claude in Okta. For more information about how to do this, check out this documentation from Anthropic.
Note: We work hard to ensure the information in the Lucid Help Center is up-to-date. However, the third-party resources linked in this section are not owned by Lucid and may change without notice. If you notice that this information is outdated, please let us know in the feedback survey linked at the bottom of this article.
FAQ
What can users access through enterprise-managed authorization?
Users can only access Lucid documents they already have permission to open. Documents owned by users outside your account can't be accessed.
How can I manage MCP access through groups or roles?
Admins can control user access to the Lucid MCP connector through enterprise-managed authorization (EMA) in three ways:
-
Lucid Enterprise Shield: Use AI distributed security in your Enterprise Shield org groups to disable MCP access for specific groups. If a user belongs to a restricted group, the connector will still show as "Connected" in Claude, but prompting it will return an error: "You do not have permissions to use Lucid MCP. Please contact your admin."
-
Claude roles: Assign specific Claude role groups during EMA setup to determine which users can access the connector.
-
Okta groups (via SCIM): Sync your Okta groups to Claude roles using SCIM, then use those roles to manage EMA and MCP access based on your existing Okta group structure.
Give feedback on this article
Have feedback about this article? Tell us about your experience here.