Summary and recommendation
BlueJeans 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.
BlueJeans was a cloud video conferencing platform acquired by Verizon in 2020 and shut down in early 2024. The information below is preserved for historical reference only - the service is no longer operational and no new accounts or migrations are possible.
Like every app in a typical SaaS stack, BlueJeans required per-user provisioning through an admin console, following a fixed role-based model with three roles: Account Owner, Administrator, and User (Host). No custom roles or per-permission granularity were supported.
Quick facts
| Admin console path | Admin Console > Users (historical; service discontinued early 2024) |
| 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 including billing, enterprise settings, and all admin functions. | All plans | Counted as licensed seat | Only one Account Owner per account; role transfer required to change ownership. | |
| Administrator | Manage users, groups, settings, and reporting within the admin console. Cannot access billing. | Cannot manage billing or transfer account ownership. | All plans | Counted as licensed seat | |
| User (Host) | Can host and join meetings, access personal meeting room, manage own settings. | Cannot access admin console or manage other users. | All plans | Counted as licensed seat | |
| Attendee / Guest | Can join meetings via link without a BlueJeans account. | Cannot host meetings or access any admin or account features. | No account required | No seat consumed | Attendee experience and features varied by meeting host settings. |
Permission model
- Model type: role-based
- Description: BlueJeans used a fixed role-based model with Account Owner, Administrator, and User (Host) roles. No custom role creation was supported. Administrators could manage users and groups but not billing.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Coarse; three fixed roles with no per-permission customization.
How to add users
- Log in to the BlueJeans Admin Console at bluejeans.com/admin.
- Navigate to the Users section.
- Click 'Add User' or 'Invite User'.
- Enter the user's email address, first name, and last name.
- Assign a role (Administrator or User).
- Select the appropriate license/plan for the user.
- Send the invitation; user receives an email to activate their account.
Required fields: Email address, First name, Last name
Watch out for:
- Adding users consumed a licensed seat immediately upon invitation.
- Users had to activate via email before they could host meetings.
- Service was discontinued in early 2024; these steps are historical only.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Yes | Admin Console > Users > Import Users (CSV upload) |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise (required SSO to be enabled; SCIM was in beta) |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: BlueJeans supported both deactivation (suspending access while retaining account data) and deletion (permanently removing the user and their data). Admins could choose either action from the Users section of the Admin Console.
- Log in to the BlueJeans Admin Console.
- Navigate to Users.
- Locate the user by name or email.
- Select the user and choose 'Deactivate' or 'Delete' from the action menu.
- Confirm the action.
| Data impact | Behavior |
|---|---|
| Owned records | Deleted users' meeting recordings and data were removed; deactivated users retained data but could not log in. |
| Shared content | Not documented |
| Integrations | Calendar and third-party integrations associated with the user were disconnected upon deletion. |
| License freed | Deactivating or deleting a user freed the licensed seat for reassignment. |
Watch out for:
- Deletion was irreversible; recordings and personal meeting room data were permanently lost.
- Deactivated users still counted against seat limits in some plan configurations (unverified for all plans).
- Service discontinued early 2024; admin console is no longer accessible.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Standard (My Meetings) | Up to 100 meeting participants, basic meeting features. | $12.49/user/month (historical) |
| Pro (My Meetings Pro) | Up to 150 participants, recording, additional features. | $17.50/user/month (historical) |
| Enterprise | Custom participant limits, SSO, SCIM provisioning (beta), dedicated support, admin controls. | Custom pricing |
- Where to check usage: Admin Console > Reports > License Usage (historical)
- How to identify unused seats: Admin Console reporting showed last login date per user, allowing admins to identify inactive licensed seats.
- Billing notes: BlueJeans was acquired by Verizon in 2020 and shut down in early 2024. All pricing figures are historical. No new subscriptions are available.
The cost of manual management
Manual provisioning in BlueJeans required admins to invite each user individually through the Admin Console, assign a role, and select a license tier. Users consumed a licensed seat immediately upon invitation, before activation, adding cost risk to every incomplete onboarding.
Identifying unused seats required manually cross-referencing last-login data from the Reports section - there was no automated reclamation. SCIM provisioning, which would have reduced this burden, was gated behind the Enterprise tier and remained in beta at shutdown.
What IT admins are saying
The most consistent friction point reported by admins was the Enterprise-only gate on SSO and SCIM, which created a steep cost barrier for mid-market teams that needed automated provisioning.
Role granularity was a secondary complaint - the three fixed roles offered no per-feature controls, making it difficult to scope admin access precisely.
When Verizon announced the shutdown in early 2024, customers flagged unclear guidance around recording data export and ownership as a significant operational risk during migration.
Common complaints:
- SCIM provisioning was only available on Enterprise tier and remained in beta at time of service discontinuation.
- Enterprise-only features (SSO, SCIM) created a significant cost barrier for mid-market customers.
- Service shutdown in early 2024 left enterprise customers scrambling to migrate meeting data and user accounts.
- Limited role granularity - no custom roles or per-feature permission controls.
- Recording data ownership and export options were unclear during the shutdown period.
- No domain-based auto-provisioning outside of SCIM/SSO Enterprise tier.
The decision
Because BlueJeans is discontinued, there is no decision to make regarding new adoption. Every app that replaced BlueJeans in a team's stack will present the same provisioning questions: what roles exist, what tier gates automation, and what happens to data on user deletion.
For historical audits, the key facts are: Enterprise plan was required for SSO and SCIM, only one Account Owner role existed per account, and user deletion was immediate and irreversible with no soft-delete option. Any active BlueJeans seats should be treated as fully offboarded; the admin console is no longer accessible.
Bottom line
BlueJeans shut down in early 2024, making all provisioning and access management workflows historical. The platform used a coarse three-role model with no custom roles, gated its only automated provisioning path (SCIM 2.0, in beta) behind the Enterprise tier, and offered no soft-delete for users.
Teams that managed BlueJeans at scale should confirm all user data and recordings were exported prior to shutdown, as deletion was irreversible and the admin console is no longer reachable.
Automate BlueJeans 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.
