Summary and recommendation
MedBridge 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.
MedBridge is a continuing education and clinical tools platform built for healthcare organizations.
Like every app gated behind an enterprise contract, its full admin capabilities - user management, reporting dashboards, and SCIM provisioning - are only accessible on the Enterprise/Organization plan.
It serves two primary user types: Organization Admins, who manage users and assign courses, and Learners/Clinicians, who access CEU/CME courses, patient home exercise programs, and clinical resources.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| SCIM available | Yes |
| SCIM tier required | Enterprise/Organization |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Organization Admin | Manages users, assigns courses, views reporting dashboards, and configures organization settings under an enterprise/organization subscription. | Enterprise/Organization | Custom pricing | ||
| Learner/Clinician | Accesses assigned and self-selected continuing education courses, patient home exercise programs (HEP), and clinical resources. | Cannot manage other users or view organization-wide reporting. | Education ($250–275/user/year) or Premium ($300–325/user/year) or Organization | $250–325/user/year (individual plans); custom for organization seats |
Permission model
- Model type: role-based
- Description: MedBridge appears to use role-based access for tenant administration and general product use, but the detailed permission matrix is not publicly documented in full.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Expect administrative access to be separated from standard user access, with exact scopes configured per tenant.
How to add users
- Log in as an administrator.
- Open settings or administration and navigate to users.
- Choose the add or invite user action.
- Enter the user's work email and assign the appropriate role.
- Save the user and complete any activation or SSO steps required by the tenant.
Required fields: Work email address, Role
Watch out for:
- Public documentation for user administration is limited, so exact labels may vary by tenant.
- If SSO is enabled, upstream IdP assignment may still be required.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise/Organization |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Public docs do not clearly document whether users are disabled, deleted, or both. Treat lifecycle behavior as tenant-specific unless confirmed in-product.
- Open the users area as an administrator.
- Locate the user to offboard.
- Disable, revoke, or remove the account using the controls available in that tenant.
- Review any integrations or service credentials associated with the departing user.
| Data impact | Behavior |
|---|---|
| Owned records | Tenant data remains in the workspace; public docs do not describe user-owned content semantics in detail. |
| Shared content | Shared dashboards, configurations, and records remain available unless separately removed. |
| Integrations | Review service credentials and integration ownership separately during admin offboarding. |
| License freed | Seat reuse behavior is contract-dependent and not publicly documented in detail. |
Watch out for:
- Offboarding should include token and integration review, not just interactive login removal.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Education | CEU/CME continuing education courses | $250–275/user/year (individual) |
| Premium | CEU/CME courses plus patient HEP and clinical tools | $300–325/user/year (individual) |
| Organization/Enterprise | All platform features with admin console, reporting, and SCIM provisioning | Custom quote |
- Where to check usage: Settings / Administration > Users and Roles
- How to identify unused seats: Review the tenant user list and any visible login or activity metadata. No public unused-seat report was verified.
- Billing notes: Organization pricing is negotiated directly with MedBridge. Individual plan pricing is publicly listed but organization seat pricing requires a sales contact.
The cost of manual management
Without automated provisioning, every app in your stack that requires manual user management adds recurring admin overhead - and MedBridge is no exception. Organization Admins must handle user adds, seat assignments, and access changes through the admin portal by hand.
Because deactivation and deletion behavior is not publicly documented, offboarding carries additional risk: there is no confirmed self-serve way to verify whether a removed user retains any access, which matters in a clinical credentialing context.
The decision
Every app with a two-tier role model requires teams to confirm whether that model fits their access control requirements before signing - MedBridge is no different. Its permission model distinguishes Admins from Learners with no publicly documented support for granular role customization; teams requiring fine-grained access controls should confirm scope with MedBridge's sales team directly.
License types split across Education ($250–275/user/year), Premium ($300–325/user/year), and Organization (custom quote) - only the Organization tier unlocks admin console, reporting, and SCIM.
Bottom line
MedBridge is a viable platform for healthcare organizations managing continuing education and clinical workflows at scale, but it operates as a relatively opaque system for IT and procurement teams.
Key admin behaviors - including deactivation logic, granular permissions, and SCIM configuration - are not publicly documented and require direct engagement with MedBridge's account team.
Organizations should factor in the evaluation friction and contract dependency before committing, particularly if automated lifecycle management or pre-purchase admin testing is a requirement.
Automate MedBridge 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.
