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

# Lucid

*Lumos supports 2 versions of the Lucid integration: **Lucid Government** for FedRAMP environments and **Lucid** for all other Lucid accounts. Setup is the same, so pick the card that matches your environment.*

## After this article

You will be able to connect Lucid to Lumos to sync users, roles, and product licenses (Lucid, Lucidspark, Lucidscale). You can also provision, suspend, deprovision, and transfer data for Lucid users from Lumos.

## Capabilities

| Functionality | Type | Sync | Provision | Description |
| - | - | - | - | - |
| Users | Account | Yes | Yes | User accounts |
| Licenses | Permission | Yes | Yes\* | Product licenses in Lucid (Lucid, Lucidspark, LucidscaleCreator, LucidscaleExplorer) |
| Roles | Permission | Yes | Yes | Roles granting access in Lucid (Billing Admin, Document Admin, Team Admin, etc.) |

> License provisioning is available with the multi-authentication version of the Lucid connector. Reach out to [support@lumos.com](mailto:support@lumos.com) to find out more.

**Account status mapping** (from the SCIM `active` field): Lucid active maps to **Active**. Lucid inactive maps to **Suspended** (contact [support@lumos.com](mailto:support@lumos.com) to map inactive users to **Staged** instead, so they can be reviewed in access reviews). When Lucid no longer returns the user, the account maps to **Deprovisioned**.

**License note:** in Lucid's admin portal, users with a Lucid or Lucidspark license show a "Lucid Suite" license. To find those users in Lumos, add both the **Lucid** and **Lucidspark** filters to the License column.

| Action | Offboarding | Access Reviews | License Management | What happens in Lucid |
| - | - | - | - | - |
| Suspend | Yes | Yes | Yes | Sets the user inactive (blocks login), removes all product licenses and add-ons, unassigns their created documents (reassign within 30 days). Reclaims a license per product removed. Lumos marks the account **Suspended** (or **Staged** if enabled). |
| Transfer data | Yes | No | Yes | Transfers documents and folders owned by the departing user (the recipient also gets edit/share on any team folder the departing user could edit/share), custom shape libraries, and Lucidscale objects (third-party credentials, AWS accounts, GCP projects, Azure subscriptions). Transferred content appears in the recipient's Documents under a folder named `From <previous user's email>`. Both users are notified by email. No impact on Lumos account status. |
| Deprovision | Yes | Yes | Yes | Permanently removes the user (reassign their documents within 30 days of deleting). Reclaims a license. Lumos marks the account **Deprovisioned**. |

A standalone **Downgrade** action (removing product licenses while keeping the user active) isn't available on this connector. The Lucid API has no unassign-license endpoint, so reclaim licenses with Suspend or in the Lucid admin panel.

By default, the Lucid **Account Owner** receives documents auto-transferred when a user is delicensed or deleted. Change the recipient in the SCIM integration settings in the Lucid Admin Panel.

## Required plan and roles

* **Lucid plan:** the **Lucid Enterprise** plan is required.
* **Lucid roles:** your Lucid user must be a **Team Admin** to perform setup. Before connecting, a **Billing Admin or Account Owner** must enable automatic team upgrades.
* **Scopes:**
  * `account.user` (Required): create, view, edit, and delete users on your account
  * `user.profile` (Required): view basic profile information (full name, username, email)
  * `account.user.transfercontent` (Provisioning only): transfer data when deleting users
* **Permission scoping:** this integration **cannot be scoped to read-only**, though some scopes can be downgraded (for example, `account.user.transfercontent` is only needed if you use provisioning or data transfer).

## Instructions

**Phase 1: Prepare Lucid**

1. Enable automatic team upgrades under **Admin** → **Licensing** (requires Account Owner or Billing Admin).
2. Contact Lucid support to enable **SCIM** in your account.
3. Generate a SCIM bearer token for Lumos under **Admin** → **App Integration** → **SCIM** and copy it.

**Phase 2: Connect in Lumos**

1. Find the Lucid card in your Lumos integrations (reconnect an existing card or add a new one).
2. Choose the option matching your environment: **Lucid Government** if you are in a FedRAMP environment, **Lucid** for all others.
3. Enter a unique identifier (for example `lumos-Lucid-1`) in the **App Instance Identifier** field.
4. Enter the SCIM token in the **API Key** field.
5. Click **Connect Lucid**.

## API Endpoints Used

<Note>
  The API endpoints this integration uses are available to logged-in Lumos customers. [Log in](/login) to view them.
</Note>

## Troubleshooting

**User counts in Lucid and Lumos don't match.** In Lumos, navigate to the Lucid app and apply filters **Account Status = Active and Suspended** and **Source = Lumos integration**. The user count in Lucid should now match the number in the lower-right corner of the Lumos user table. If it still doesn't, open a ticket with Lumos Support (Slack or [support@lumos.com](mailto:support@lumos.com)) including the User CSV pulled directly from the app (with a note on how it was pulled) and the link to your Lucid app in Lumos with the filters applied.

**Suspended or deleted users' documents went missing.** Suspend and Deprovision unassign the documents a user created. Reassign them in the Lucid admin panel within 30 days, or use **Transfer data** first. Auto-transferred documents go to the Account Owner unless you change the recipient in Lucid's SCIM integration settings.

**Inactive users don't show up in Access Reviews.** Inactive Lucid users map to **Suspended** by default. Contact [support@lumos.com](mailto:support@lumos.com) to map them to **Staged** so they appear in access reviews.

**Inactivity workflows deprovision the wrong users.** Lucid-native last-login data can be unreliable. For inactivity-based workflows, prefer last-login data from your IdP (for example, the Okta group that assigns the Lucid license) as the source of truth.