Integrating Lucid with Okta enables your users to authenticate using SAML single sign-on through Okta. Furthermore, our SCIM integration allows admins to provision and deprovision users within Okta itself, without having to sign in to Lucid.
The following tutorial walks through the process of integrating Okta with Lucid. You will need admin privileges in both Okta and Lucid to complete this integration.
Plan availability: Enterprise only.
- Available on FedRAMP accounts.
- Read the Lucid Plans article for more information about what is available on your account or the Upgrade your Lucid account article for instructions to upgrade.
Note: The information in this article also applies to Lucid FedRAMP (GovSuite) accounts with no separate steps or custom Okta app required. Generating your ACS URL, SCIM Base URL, and bearer token from your Lucid GovSuite admin panel automatically creates a FedRAMP-compatible configuration.
Supported features
SAML SSO Capabilities:
- SP-initiated SSO
- IdP-initiated SSO
- JIT (Just-In-Time) Provisioning
SCIM Provisioning Capabilities:
- Create Users
- Update User Attributes
- Deactivate Users
- Push Groups
Configure the SAML integration for Lucid
Follow the below instructions exactly regardless of whether you are using Lucidchart, Lucidspark, or both.
Note: The steps outlined in this section are for setting up SAML with Lucid's SCIM for admin management app, rather than Lucid's SCIM for content access app. If you are using a Lucid SCIM for content access app, but not using a Lucid SCIM for admin management app in Okta, you can follow these instructions for your Lucid for content access app instead. To learn more, refer to the Configure SCIM for the Lucid Suite in Okta section below.
In Lucid:
- Select Admin.
- Click Security in the left-hand menu.
- From the dropdown, select Authentication.
-
Select Configure to the right of the “Allow SAML authentication” option to navigate to your SAML Activation page in Lucid. You will not be able to use SAML until you have populated your domain and uploaded metadata.
-
Under "Lucid sign-in URL," enter your Domain name.
-
Ensure the domain you are using is not already in use, since it is used to uniquely identify your account during SSO.
-
Ensure the domain you are using is not already in use, since it is used to uniquely identify your account during SSO.
- Click Save changes.
- Copy the ACS URL from Lucid (it will be needed in Okta).
In Okta:
-
Browse the Okta Integrations Network and search “Lucid”.
- After you have added the Lucid app to Okta, you can configure the SAML integration so that end users on your Okta instance can authenticate using SAML sign-on through Okta.
-
In the General Settings section of the Lucid for admin management app in Okta:
- Paste the ACS URL from Lucid in as the “SAML URL”
-
Select whether you would like to display "diagramming" and/or "whiteboarding". Each will appear in your users app gallery to facilitate IdP-initiated sign-on.
- In the "Sign On" tab of Okta, navigate to SAML Signing Certificates.
- Click Actions.
- Select View IdP metadata.
-
Download the metadata by right-clicking anywhere on the XML page, selecting Save As, and saving it as an XML file (e.g., “metadata.xml”).
-
This XML file (metadata) contains instructions that Lucid will need to communicate with Okta. You will upload the saved file to Lucid.
-
This XML file (metadata) contains instructions that Lucid will need to communicate with Okta. You will upload the saved file to Lucid.
In Lucid:
- Open the Lucid admin panel.
- Click App integration from the navigation on the left side.
- Select General from the navigation options.
- Under "Enabled integrations", click Settings from the "SAML" tile.
-
Scroll down on the SAML Activation page and click + Add identity provider to upload the XML file you downloaded from Okta.
-
The metadata will populate the following fields:
-
The metadata will populate the following fields:
-
Click Test SAML connection to verify that Lucid is properly communicating with Okta.
- The connection will only work if the Lucid for admin management app has been assigned to your test user in Okta. You can assign the app to users in the Assignments section of the app page.
-
The test may fail if you have not enabled SAML as an authentication method. If this occurs, navigate to the Authentication page in the Security settings of your Lucid admin panel, and verify “Allow SAML authentication” is checked.
You have the option to use encrypted assertions for the identity providers you add for SAML to your Lucid account. To learn more, refer to our SAML overview article.
Note: You can select the default authentication method in Lucid, after you have checked the methods that you would like to allow as sign in options above. Users will be prompted to sign in using the default authentication you set up in the Authentication page.
Create users upon login with SAML
Once you have configured SAML with Okta for your Lucid account, you can set up Just-In-Time (JIT) provisioning so that users assigned Lucid access in Okta who do not have a Lucid account will have an account created for them upon their first login.
Note: For JIT provisioning to work as intended, you should have domain control enabled and have the user verification method set to SAML.
You can customize Just-In-Time provisioning in the license settings section of your Lucid admin panel, depending on the access you want users to have. Here are the options:
- If you would like all users to come onto your Lucid account with full-edit licenses, choose the following settings:
- Under the “Access eligibility” section, select Eligible for full access.
- Under “Customized eligibility criteria”, select Instant access.
- If you want all users to come in as limited-access users, under the “Access eligibility” section select Only eligible for limited access.
- Your users will still be able to request full-edit licenses. Depending on the “When a user requests a license” setting, you can automatically grant licenses to users upon their request, or you can turn those requests into pending requests in your user list.
Add user attributes via Just-in-Time (JIT) provisioning
JIT provisioning uses the SAML protocol to create a Lucid user when someone assigned Lucid access in your Okta instance logs in to Lucid for the first time. You can also configure SAML to send additional attributes to Lucid for these users, such as the user's first name, last name, and email address.
Note: License values cannot be sent to Lucid via JIT provisioning. This means you can’t update, delete, or deactivate a user using JIT provisioning in Lucid since it only works during a user's first login. Any update, deletion, or deactivation must be done via SCIM (if applicable), or manually from the user management page of the Lucid admin panel.
Follow these steps to configure first name, last name, and email attributes:
- Log in to your Okta account.
- Navigate to the Lucid for admin management app in Okta
- Select the Sign On tab.
- In the upper-right corner of the Sign On section, select Edit.
- Click the arrow to the left of “Attributes (Optional)” to expand the menu.
- Configure a user’s first name:
- Add a title to the name field. This value doesn’t have to match the Value dropdown section.
- In the name format field, select Unspecified from the drop-down list.
- Click on the drop-down menu beneath “Value”.
- Select user.firstName from the dropdown.
- To add another field click Add Another.
- Repeat the instructions for last name and email with the specified name field and value field expressed below:
- To add a user’s last name:
- Add a title to the name field.
- Select user.lastName from the Value fields dropdown
- To add a user’s email:
- Add a title to the email name field.
- Select user.email from the Value field dropdown
- To add a user’s last name:
- After adding the user attributes described in these steps, you can expect your Okta page to look like this:
- Scroll to the bottom of this inner window.
- Click Save.
Now, when a user signs in for the first time and creates their Lucid account, they will have their first name, last name, and email address values properly set up.
Configure SCIM for the Lucid Suite in Okta
To create users before their first login through Okta, set up the Lucid SCIM integration by following the steps below.
Note: The instructions in this section for setting up a SCIM app are relevant if you are setting up SCIM for the first time on your Lucid Enterprise account. If you were already using SCIM prior to October 22nd, 2024, you need to migrate to the new organizational groups experience, refer to our Okta migration article for instructions.
Additionally, If you created your Lucid app in Okta before May 13, 2026, it may not automatically sync optional user profile fields such as manager and department. To set up these mappings, please see this post from the Lucid Community.
Before configuring SCIM, confirm that you are on an Enterprise account with an up-to-date pricing plan. To upgrade, contact sales.
Once you have followed the pre-configuration steps listed above, you can configure both SCIM for admin management and SCIM for content access apps for the Lucid Suite in Okta by generating separate bearer tokens in Lucid and then using them in Okta. To learn more about the differences and value of each app, refer to our SCIM overview for Lucid article.
Enable SCIM and generate a bearer token in Lucid
- Log in to Lucid as an account owner or account admin.
- Select Admin from the menu to the left.
- Select App integration in the left-hand navigation menu.
- On the relevant SCIM tile, select Settings (or Install).
- To set up both apps, you will need to separately follow the remaining steps for SCIM for admin management and SCIM for content access. You will generate a separate bearer token for each app.
- Under the bearer token section, click Generate token.
- The Lucid base URL and bearer token will be needed for the next steps in Okta.
Configure integration(s) and use bearer token(s) in Okta
Depending on whether you are looking to use SCIM for admin management, SCIM for content access, or both, the steps here will slightly differ.
Configuration for SCIM for admin management
- Log in to Okta as an admin.
- Open the Okta Admin Console and navigate to your Lucid app.
- Under the "General" tab, under the "App Settings" section, add the SCIM Base URL.
- This URL can be copied directly from the SCIM for admin management page in Lucid.
- This URL can be copied directly from the SCIM for admin management page in Lucid.
- Under the "Provisioning" tab, click Configure API Integration.
- Check the box next to "Enable API Integration".
- A text field will appear where you can add your bearer token that was generated by Lucid.
- A text field will appear where you can add your bearer token that was generated by Lucid.
- Paste the bearer token generated by Lucid from the SCIM for admin management into the API token field.
- Keep in mind that if you are setting up both Lucid SCIM apps, this is a separate bearer token from the SCIM for content access token. Be sure to use the correct one with each app.
- Make sure “Import Groups” is not checked (unless you want your existing Lucid org groups imported to Okta).
- Click Save.
Once the Lucid and Okta connection is established, you can start using the SCIM connection to provision users and groups and manage licenses. See the sections below for further information.
Configuration for SCIM for content access
- Log in to Okta as an admin.
- Browse the Okta Integrations Network and search “Lucid”.
- Create a new Lucid app.
- If you are also using SCIM for admin management, we suggest naming this app “Lucid for content access” to differentiate the two.
- In the General Settings section of the Lucid for content access app in Okta, select whether you would like to display "diagramming" and/or "whiteboarding".
- If you are also using SCIM for admin management, we suggest unchecking both “diagramming” and “whiteboarding” in this app to prevent duplicate Lucid tiles for end users.
- Under the "Provisioning" tab, click Configure API Integration.
- Check the box next to "Enable API Integration".
- A text field will appear where you can add your bearer token that was generated by Lucid.
- Paste the bearer token generated by Lucid from the SCIM for content access tile into the API token field.
- Keep in mind that if you are setting up both Lucid SCIM apps, this is a separate bearer token from the SCIM for admin management token. Be sure to use the correct one with each app.
- Make sure that “Import Groups” is not checked (unless you want your existing Lucid teams imported to Okta).
- Click Save.
Set up SCIM for admin management
The groups that you set up for SCIM for admin management will be used to manage licensing and granular admin controls at scale, including attribute management (e.g. cost center, region, etc). These groups can also be used to automatically provision users and Lucid org groups to reflect company hierarchy.
Set up an All users group
Follow these steps to set up an All users group in Okta.
- Navigate to the “Assignments” tab of the Lucid application in Okta.
- Click Assign from the top-left of the "Assignments" page.
- From the dropdown options, select Assign to Groups.
- Search for your “All users” group.
- Having an All users group (which will most likely have a different name for your company) is important as it is typically used to assign all users at your company to this Okta application. This is what enables them to sign in and see the Lucid tiles within the main Okta applications page.
- Click Assign.
Note: Each user on your account should belong to the “All Users” assignment, regardless of which push group they may belong to.
Assign license groups via group push
Group Push in Okta allows admins to provision groups from Okta as organizational groups in Lucid. These Okta push groups are used to license and delicense users in Lucid.
To create new push groups that work with Lucid organizational groups, follow these steps:
- Select the Push Groups tab from the menu at the top of the Lucid app page in Okta.
- Click + Push Groups.
- From the dropdown options, select Find groups by name.
- We recommend customizing licensing groups.
- These groups will be used to assign a user a license in Lucid based on their membership to the group.
- Removing users from a licensing group will delicense them to free up licenses for others to use.
- Click Save & Add Another if you need to add another group.
- Click Save when you’ve added your last group.
Note: A user can belong to only one organizational group, but you can have as many license user groups as you need.
View Okta push groups as organizational groups in Lucid
At this stage of the process, we recommend double-checking you see the expected Okta push groups as organizational groups in Lucid, which confirms the SCIM group setup was successful. To access the organizational groups page in Lucid, follow these steps:
- Navigate to the Lucid admin panel.
- Select Groups from the left-hand navigation menu.
- From the dropdown menu, click Organizational groups.
You can expect to see your Okta push groups as organizational groups on this page of the Lucid admin panel.
Configure license settings for each group
You’re now ready to configure the license settings for each of your organizational groups. This ensures that users are licensed or delicensed appropriately when they are added to or removed from any of these groups.
To access license settings, follow these steps:
- Navigate to the Lucid admin panel.
- Select License settings from the left-hand navigation menu.
- From the dropdown menu, click Lucid Suite settings.
- Proceed to the appropriate set of steps below to customize license settings for each organizational group.
Configure license setting for licensing users group:
- Select your desired licensing group from the list of organizational groups on the left-hand side of the licensing page.
- Under the “Access eligibility” section, select Eligible for full access.
- Under “Customized eligibility criteria”, select Instant access.
- Click Save changes.
- Repeat these steps for any additional licensing groups.
Note: These settings make it so any users added to this group via SCIM automatically receive a Lucid Suite license.
You have now completed all the steps to reconfigure the Lucid app. License settings will now be managed via the organizational groups created via SCIM.
Assign roles to users with SCIM
To define a user's role, you will use the strings "AccountAdmin" and "BillingAdmin." To apply both admin roles to a user, you will need to assign multiple roles to the users or groups rather than a single role with a concatenated string.
Note: The strings above must match the capitalization expressed for these user roles.
Set up SCIM for content access
SCIM for content access is ideal for managing collaboration and document sharing. It allows you to provision and deprovision users and teams directly from your identity provider, but doesn’t manage licensing. To set up a SCIM for content access app in Okta, follow the steps from the Configure SCIM for the Lucid Suite in Okta section, then return here to continue with the steps to customize your user groups.
We recommend creating these groups for sharing by department, location, etc. depending on your account needs.
Note: SCIM for content access is currently unavailable for accounts with legacy groups (sharing). To learn more about if that applies to your account, refer to our Lucid admin panel: Groups management article.
Assign users under Assignments tab in Okta
- Navigate to the “Assignments” tab of the Lucid SCIM for content access app you created in Okta.
- Click Assign from the top-left of the Assignments page.
- From the dropdown options, select Assign to Groups.
- Search for the relevant Groups you will be using for sharing.
- These could look like groups specific to your departments, locations, etc. These can align with and match the push groups you will use in the next section.
- Alternatively, you can also use your “All users” group that you may be using for the SCIM for admin management app. Refer to the Set up an All users group section if you wish to use that.
- Click Assign.
Add users to push groups in Okta
Group Push in Okta allows admins to push groups from Okta to Lucid and manage Lucid teams for sharing through Okta.
To create new push groups for content access, follow these steps:
- Select the Push Groups tab from the menu at the top of the Lucid app page in Okta.
- Click + Push Groups.
- From the dropdown options, select Find groups by name.
- Add and customize the groups that you want for document sharing, which may look like groups by department, location, etc.
- Click Save & Add Another if you need to add another group.
- Click Save when you’ve added your last group.
Access teams from Lucid admin panel
The groups that you create will be visible in the Lucid admin panel by following these steps:
- Navigate to the Lucid admin panel.
- Select Groups from the left-hand navigation menu.
- From the dropdown menu, click Teams.
FAQ
What happens to documents when I delicense a user via SCIM?
When you delicense a user via SCIM, their documents will be transferred to another user on your Enterprise account. The document transfer will occur 24 hours after delicensing via SCIM.
By default, the account owner will be the recipient of the documents that are automatically transferred upon delicensing a user. You can change the recipient of the transferred documents by navigating to the SCIM integration settings in the Lucid admin panel and selecting Modify default owner to the right-hand side of the email address. See the screenshot below for reference.
Clicking Modify default owner redirects you to the “Compliance settings” page of the admin panel where you can change who the default document owner on your account is. Refer to our Lucid admin panel: Compliance settings article for additional details.
Does JIT provisioning handle updates, deletions, and deactivations of users in Lucid?
No. JIT provisioning cannot update, delete, or deactivate a user in Lucid since it only works during a user's first login. That means any update, deletion, or deactivation would need to be done within the Lucid Admin Panel if you are not using SCIM.
If you want to update users and allow for automation of deactivating users, you should use SCIM instead of Just-In-Time provisioning.
Resources
To learn more about this feature or to ask additional questions, explore the additional resources below. These resources are available in English only.
Community post
Instructions to update IdP metadata certificate (renew SSO cert)
Give feedback on this article
Have feedback about this article? Tell us about your experience here.