Summary and recommendation
Epic 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.
Epic is a Hyperspace-based electronic health record platform used primarily by hospitals and large health systems.
Unlike most enterprise SaaS tools, it has no web-based admin console - all user management happens inside the Hyperspace client application itself.
Every app or identity system that needs accurate user state from Epic must account for this constraint from the start.
User management documentation is gated behind the Epic UserWeb customer portal and requires customer credentials to access.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| SCIM available | No |
| SCIM tier required | Enterprise |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| System Administrator | Full access to Epic system configuration, user account management, security class assignment, and audit tools. | Epic's user management documentation is gated behind the Epic UserWeb customer portal and is not publicly available. Role names and permissions vary by Epic module and customer configuration. | |||
| End User (Clinician/Staff) | Access determined by assigned security class and user record configuration within Epic. | Cannot modify their own security class or access rights. | Permissions are highly granular and configured per-organization by Epic analysts or system administrators. There is no standard universal role set documented publicly. |
Permission model
- Model type: role-based
- Description: Epic uses a Security Class system where each user is assigned one or more security classes that define access to activities, reports, and data. Security classes are configured per-organization and can be highly customized. This is documented within Epic UserWeb but not in publicly accessible documentation.
- Custom roles: Yes
- Custom roles plan: Not documented
- Granularity: Activity-level and record-level access controls configured via security classes; granularity is high but configuration is organization-specific.
How to add users
- Access Epic's user management tools via the Epic hyperspace application (not a web-based admin console).
- Navigate to the user record creation screen (typically via a search or admin activity).
- Enter required user fields including name, login ID, and security class assignment.
- Assign appropriate security classes, user settings, and provider record linkage if applicable.
- Save the user record; the user can then log in with their assigned credentials.
Required fields: User name, Login ID, Security class assignment
Watch out for:
- Epic is a client-server or Hyperspace-based application; user management is performed inside the Epic application itself, not via a standalone web admin console.
- Exact steps and field names vary by Epic version (e.g., Epic 2023, Epic 2024) and by organization-specific configuration.
- User creation workflows are documented in Epic UserWeb, which requires customer credentials to access.
- Provider users typically require linkage to a provider record in addition to a user account.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | Unknown | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Epic's official documentation on user deactivation versus deletion is not publicly available. Based on general EHR compliance requirements (audit trail preservation), deactivation rather than deletion is the standard practice, but this cannot be confirmed from publicly accessible sources.
- 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, service accounts, or 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 content and workspace records typically remain available unless separately removed or reassigned. |
| Integrations | Review service credentials, workflow ownership, and integrations separately during admin offboarding. |
| License freed | Seat reuse behavior is contract-dependent and not publicly documented in detail. |
Watch out for:
- Epic user management documentation is behind the Epic UserWeb customer portal and is not publicly verifiable.
- Healthcare regulatory requirements (HIPAA audit trail obligations) typically require that user records and associated audit logs be retained even after a user is deactivated.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Named User | Access to the tenant features exposed to the assigned role. Seat entitlements are generally tied to the subscription contract. | Custom pricing; determined by contract and plan. |
- 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: Epic licensing is negotiated directly with Epic Systems on a custom contract basis. Pricing ranges from approximately $1,200 to over $500 million depending on organization size and modules. No public per-seat pricing is available.
The cost of manual management
Epic licensing is negotiated directly with Epic Systems on a custom contract basis, with no public per-seat pricing available. Pricing ranges from approximately $1,200 to over $500 million depending on organization size and modules selected.
Because every app in your stack that touches Epic provisioning requires manual coordination inside Hyperspace, the operational cost scales with headcount and staff turnover - not with any published tier.
The decision
Epic's permission model is role-based via a Security Class system, where each user is assigned one or more security classes that control access at the activity and record level. Security classes are organization-specific and highly configurable, but that configurability comes with maintenance overhead - dedicated Epic-certified analysts are typically required to manage them.
Every app downstream that depends on role accuracy is exposed to drift when security class changes are not applied promptly. Provider users also require linkage to a separate provider record in addition to a standard user account, adding a step that has no equivalent in most SaaS provisioning flows.
Bottom line
Epic is not a tool you provision through a standard IT workflow. Every app or identity system that needs to stay in sync with Epic user state requires either manual Hyperspace administration or a custom integration built on Epic's FHIR API.
The security class model is powerful but demands ongoing analyst attention, and the lack of public documentation means new administrators are dependent on Epic training resources or internal institutional knowledge to operate it effectively.
Automate Epic 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.
