> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oleria.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lucid

> Connect your Lucid Enterprise account to Oleria to continuously discover user and group access across your visual collaboration platform.

Lucid is a visual collaboration platform that includes Lucidchart and Lucidspark. Connect your Lucid Enterprise account to Oleria to bring its users and groups into your identity and access graph.

## What Oleria discovers

User accounts and profile attributes, and Lucid organizational groups with their members, synced from Lucid's SCIM API. Oleria uses this data for access reviews, refreshed on Oleria's [regular sync schedule](https://docs.oleria.com/integrations/overview.md#sync-model).

## Prerequisites

* A Lucid **Enterprise** account. Lucid offers SCIM only on Enterprise. Lucid says the base URL can be different for accounts in its FedRAMP environment. If your account is there, contact us before you connect, so we can confirm Oleria can reach that URL.
* An account owner or account admin in Lucid, to generate the SCIM bearer token.
* Admin access on the Oleria platform to add a new integration.

## Get your SCIM credentials from Lucid

Lucid has two SCIM integrations, and each has its own bearer token. Use **SCIM for admin management**: with its token, Lucid's SCIM API returns your users and your Lucid organizational groups. A **SCIM for content access** token returns Lucid teams instead.

**1. Open SCIM for admin management**

Sign in to Lucid as an account owner or account admin. Select **Admin**, then **App integration**. On the **SCIM for admin management** tile, select **Settings** (or **Install**).

**2. Generate your Authentication Token**

> [!WARNING]
>
> If your identity provider (for example, Okta or Microsoft Entra ID) already provisions Lucid through this integration, it uses this integration's bearer token, and Lucid shows one token per integration. Before you generate a new one, confirm with Lucid that your identity provider's token keeps working, so your existing provisioning isn't interrupted.

In the bearer token section, select **Generate token**, and copy the token. You'll paste it into Oleria in the next section.

> [!NOTE]
>
> Lucid says that with **SCIM for admin management** you may need to turn on **Auto-purchase licenses** in Lucid, so that provisioning can license and de-license users automatically.

## Connect Lucid to Oleria

**1. Open the integration**

Go to your Oleria workspace, select **Integrations**, then select the **Lucid** tile.

**2. Complete the connection form**

Fill in the connection form:

| Field | Notes |
| :- | :- |
| Instance Name | Optional. Short, recognizable label for this connection (for example, `lucid-prod`). |
| SCIM Base URL | Required. `https://users.lucid.app/scim/v2`. |
| Authentication Token | Required. The SCIM for admin management bearer token from Lucid. |

**3. Save the integration**

Select **Connect** to validate the credentials and save the integration.

> [!NOTE]
>
> A token works only with the integration it was generated for. Oleria identifies a Lucid connection by its base URL, which is the same for every Lucid account, so you can connect one Lucid account, with one integration's token, per Oleria workspace.

## Verify the integration

Confirm the new instance appears on the **Connected** tab of your Oleria **Integrations** page with a status of **Healthy**. Oleria syncs users and groups from Lucid on its [regular sync schedule](https://docs.oleria.com/integrations/overview.md#sync-model) once the initial sync completes.

> [!NOTE]
>
> If you regenerate the SCIM token in Lucid, update the **Authentication Token** in Oleria by editing the integration.

## Remediation actions

Oleria can also take these actions in Lucid when the SCIM token can update users and groups:

* Enable or disable a user account
* Add or remove a user from a group
* Create a new user or group

> [!NOTE]
>
> Oleria doesn't check the token's permissions until an action runs. If an action fails, confirm the token can update users and groups in Lucid.

## Known limitations

* Lucid doesn't document whether its SCIM API lists deactivated users. If it doesn't, a user deactivated (by Oleria or in Lucid) drops out of Oleria's inventory after the next sync and can't be selected for **Enable**. To re-enable a user Oleria disabled, an Oleria administrator can select **Undo** on that disable action in [Action Center](https://docs.oleria.com/governance/view-remediation-actions.md) within 7 days. After that, re-enable the user in Lucid.
* A Lucid user can belong to only one organizational group.

## Contact us

For questions about this integration, contact us at [support@oleria.com](mailto:support@oleria.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.