Summary and recommendation
Lucid Chart user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Lucidchart's Admin Panel gives Owners and Admins a single console at lucid.app/admin to invite users, assign roles, and monitor seat consumption across every app-connected workflow that touches Lucid access. The permission model is fixed: Owner, Admin, Editor (User), and Collaborator/Viewer - no custom roles exist at any plan tier.
Document-level permissions (view, comment, edit) are set independently per document or shared space, separate from account-level roles.
Quick facts
| Admin console path | Team Menu (top-right avatar) → Admin Panel → Users tab |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Enterprise |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Account Owner | Full account control: billing, plan changes, Admin Panel access, all admin actions. Only one Owner per account. | Cannot be demoted by another admin; ownership must be explicitly transferred. | All paid plans | Counts as a licensed seat | Ownership transfer requires the current Owner to initiate it; admins cannot reassign ownership themselves. |
| Admin | Manage users, assign roles, configure SSO/SCIM, manage groups, view usage reports, adjust account settings. Cannot change billing or plan. | Cannot modify billing details or upgrade/downgrade the plan; cannot transfer ownership. | Team or Enterprise | Counts as a licensed seat | Admin role is available on Team plans but SCIM and SSO management within the Admin Panel require Enterprise. |
| User (Editor) | Create, edit, and share documents up to plan limits. Can be added to groups and shared spaces. | Cannot access Admin Panel, manage other users, or change account settings. | Any paid plan (Individual, Team, Enterprise) | Counts as a licensed seat | On Team plans, each User seat is billed; adding users beyond purchased seats triggers auto-upgrade if enabled, or blocks addition if disabled. |
| Collaborator / Free Viewer | View and comment on documents shared with them. Can edit if granted explicit edit access on a per-document basis. | Cannot create new documents, cannot access team folders independently, no Admin Panel access. | Free (external collaborators do not require a paid seat on Enterprise; behavior varies by plan) | Does not consume a licensed seat when acting as view-only collaborator on Enterprise; may consume a seat on Team if granted edit rights | Granting a Collaborator edit rights on Team plans may automatically consume a paid seat depending on auto-upgrade settings. |
Permission model
- Model type: role-based
- Description: Lucidchart uses a fixed set of account-level roles (Owner, Admin, User/Editor, Collaborator/Viewer). Document-level sharing permissions (view, comment, edit) are set independently per document or folder. There are no fully custom roles; admins assign from predefined role tiers.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Account-level role controls Admin Panel access and seat consumption. Document-level permissions (view/comment/edit) are set per document or shared space, independent of account role.
How to add users
- Navigate to lucid.app/admin and sign in as Owner or Admin.
- Select the 'Users' tab in the left sidebar.
- Click 'Invite users' (or 'Add users' depending on plan UI).
- Enter one or more email addresses in the invitation field.
- Select the role to assign (Admin or User).
- Click 'Send invitations'. Invitees receive an email to accept and join the account.
- Alternatively, enable domain capture so anyone signing up with a matching email domain is automatically added to the account.
Required fields: Email address of invitee, Role assignment (Admin or User)
Watch out for:
- If auto-upgrade is disabled and no seats are available, the invitation will fail or be queued until a seat is freed or purchased.
- Invited users must accept the email invitation before they appear as active members; pending invitations still consume a seat reservation on some plan configurations.
- Domain capture (auto-join) must be configured separately under Admin Panel → Security settings and requires domain verification.
- On Team plans, the minimum seat count is 3; reducing below 3 is not permitted.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Yes | Admin Panel → Users tab → Invite users → 'Import CSV' option (CSV must contain email addresses, one per row; optional columns for first name, last name) |
| Domain whitelisting | Yes | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: Lucidchart allows admins to remove (deactivate/delete from the account) users via the Admin Panel. Removing a user revokes their access to the team account and frees their licensed seat. The user's documents that were shared with the team remain accessible to the account; documents owned solely by the removed user may need to be transferred. Lucid distinguishes between 'removing from account' (access revoked, seat freed) and full data deletion (requires a separate data deletion request per Lucid's privacy policy).
- Navigate to lucid.app/admin and sign in as Owner or Admin.
- Select the 'Users' tab.
- Locate the user by name or email using the search field.
- Click the three-dot (⋯) menu or checkbox next to the user's name.
- Select 'Remove user' (or 'Deactivate').
- Confirm the action in the dialog. The user is immediately removed from the account and loses access.
| Data impact | Behavior |
|---|---|
| Owned records | Documents owned by the removed user remain in the account if they were stored in team folders or shared spaces. Documents stored only in the user's personal space may become inaccessible unless transferred prior to removal. Admins should transfer document ownership before removing the user. |
| Shared content | Shared documents the user had access to remain intact for other collaborators. The removed user loses access immediately. |
| Integrations | Any personal integrations (e.g., Google Drive, Confluence) configured by the user are disconnected. Team-level integrations configured by an admin are unaffected. |
| License freed | The seat is freed immediately upon removal and becomes available for reassignment or reduces the billable seat count at the next billing cycle, depending on plan terms. |
Watch out for:
- Documents stored only in the removed user's personal (private) folder may be lost if ownership is not transferred before removal; Lucid recommends transferring ownership first.
- Removing a user does not automatically delete their data from Lucid's systems; a separate data deletion request must be submitted for GDPR/CCPA compliance.
- If the removed user was the sole owner of shared team content, other team members may lose edit access to those documents until an admin reassigns ownership.
- On Enterprise with SCIM, deprovisioning via the IdP is the recommended removal path; manual removal and SCIM deprovisioning can conflict if both are used simultaneously.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Editor (Full User) Seat | Full create/edit access to Lucidchart documents, Admin Panel access (if Admin role), collaboration features, integrations. | Team: ~$9/user/month (billed annually, min 3 users); Enterprise: ~$199/user/year with volume discounts ($189 for 25+, $179 for 50+) |
| Free / Collaborator (no seat) | View and comment on shared documents. On Enterprise, external collaborators do not consume a paid seat when in view/comment-only mode. | $0 - does not consume a paid seat in view-only mode on Enterprise |
- Where to check usage: Admin Panel (lucid.app/admin) → Users tab shows total active users, pending invitations, and seat consumption. The 'Billing' or 'Licensing' tab shows total purchased seats vs. used seats.
- How to identify unused seats: Admin Panel → Users tab → sort or filter by 'Last active' date to identify users who have not logged in recently. Lucid does not provide a dedicated 'inactive users' report natively; admins must manually review last-active timestamps.
- Billing notes: Team plan seats are billed at a minimum of 3. Auto-upgrade (enabled in Admin Panel → Licensing settings) automatically purchases additional seats when invitations exceed current seat count; disabling auto-upgrade prevents over-provisioning but also blocks new invitations when seats are full. Enterprise pricing is negotiated annually with volume discounts. SCIM bearer token generation requires auto-upgrade to be enabled in Licensing settings on Enterprise.
The cost of manual management
Without automated provisioning, every app in your stack that touches Lucidchart access requires a manual trip to the Admin Panel. Identifying unused seats means hand-sorting the Users tab by last-active date - there is no native inactive-user report.
Pending invitations can silently hold seat reservations even when the invitee never accepts, and document ownership must be manually transferred before removing a user or content may become inaccessible.
What IT admins are saying
The most consistent friction point reported by admins is the Auto-upgrade toggle: it must be enabled in Licensing settings to generate a SCIM bearer token, but it also allows uncapped seat purchases if left on without governance.
Admins frequently discover this only after unexpected charges appear on their invoice. A secondary complaint is that removing a user and deprovisioning via SCIM simultaneously can create account inconsistencies - Lucid recommends choosing one removal path per account.
Common complaints:
- Auto-upgrade setting is not prominently documented; admins discover it only when SCIM token generation fails or unexpected seat charges appear.
- Enterprise pricing is not publicly listed in detail; requires contacting sales for exact quotes beyond the published per-user rates.
- No native 'inactive user' report in the Admin Panel; identifying unused seats requires manual review of last-active dates.
- Document ownership transfer must be done manually before removing a user; there is no automated ownership reassignment workflow.
- Pending invitations may hold seat reservations even if the invitee never accepts, consuming available seats.
- Removing a user via the Admin Panel and via SCIM deprovisioning can create inconsistencies if both methods are used on the same account.
- Auto-upgrade requirement can be confusing
- Enterprise pricing not transparent
- Bearer token generation requires specific settings
The decision
Manual administration works for small, stable teams where seat counts change infrequently, but it becomes a liability once every app in your environment needs consistent, auditable access records. There is no bulk ownership reassignment, no automated inactive-user detection, and a minimum seat floor of three on Team plans.
Enterprise accounts with an IdP already in place should treat SCIM provisioning as the default path, not an optional enhancement. Admins on Team plans should note that SSO and SCIM management within the Admin Panel require an Enterprise upgrade.
Bottom line
Lucidchart's manual admin workflow is straightforward for day-to-day role assignments and invitations, but it carries real operational risk at scale.
The absence of an inactive-user report, the manual document-ownership transfer requirement, and the Auto-upgrade toggle's dual role as both a billing control and a SCIM prerequisite create compounding blind spots.
Teams managing more than a handful of seats, or operating under compliance requirements around access revocation, will find the manual path insufficient without supplemental tooling or IdP-driven SCIM automation.
Automate Lucid Chart workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
