Administration
Roles and permissions in Single Sign-On
Each role in Single Sign-On: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Single Sign-On as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.
On this page
Who can see and do what in Single Sign-On. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Imprivata as part of the managed service.
Roles
Clinical informatics lead
CMIO, CNIO, clinical informatics manager. Represents clinicians: decides which applications need sign-on profiles first and reports where sign-on gets in the way of care.
- Sees: Applications with sign-on profiles and their status; Profile failures reported by clinicians; Planned application upgrades that affect sign-on
- Does: Requests profiles for new applications; Sets priorities for profile work; Joins user testing of profiles before release; Raises clinician feedback at the monthly service review
- Cannot: Change authentication or timeout policies; Make changes directly in Imprivata
- Approvals: Approves profile changes that affect clinical workflows; policy changes need the HIPAA security officer.
- Notified about: Profiles ready for testing, upgrades scheduled, and profile incidents affecting clinicians.
Client IT identity team
Identity and access manager, Active Directory engineer, end-user computing manager. Owns the directory, workstations and virtual desktops that Imprivata depends on, and is Moraph's technical counterpart.
- Sees: The full Imprivata configuration and its health; The configuration baseline and change history; Service reports and open incidents
- Does: Approves technical change requests; Maintains directory accounts and groups that drive sign-on; Deploys the Imprivata agent through workstation images; Tells Moraph about application upgrades and new workstations; Joins the monthly service review
- Cannot: Change authentication policy without the HIPAA security officer; Edit the change record after the fact
- Approvals: Approves technical changes; policy changes also need the HIPAA security officer.
- Notified about: Incidents, vendor notices affecting you, and change requests waiting for approval.
HIPAA security officer
HIPAA security officer, CISO, identity governance lead. Sets authentication, timeout and lock requirements and uses the service's records as evidence of access controls.
- Sees: Authentication and timeout policies and every change to them; Administrator accounts, including Moraph staff; Two-factor signing setup for EPCS where it applies; Sign-in records within the service's retention
- Does: Approves authentication, timeout and lock policies; Approves exceptions such as longer timeouts in specific areas; Reviews administrator access periodically; Requests sign-in records for investigations; Uses service reports for risk analysis and audits
- Cannot: Edit or delete sign-in or change records; Make configuration changes directly in Imprivata
- Approvals: Approves policy changes and exceptions.
- Notified about: Policy exceptions requested, administrator access reviews due, and security-relevant incidents.
Badge office
Security badging coordinator, HR onboarding staff. Issues badges and helps clinicians enroll, replace or remove them.
- Sees: Badge enrollment status for a person they are helping; Badges reported lost
- Does: Issues and replaces badges; Helps clinicians enroll a new badge; Removes enrollment for lost badges
- Cannot: Change policies or profiles; See sign-in history
- Approvals: None; badge issuance follows your existing identity verification process.
- Notified about: Enrollment problems routed back from the service desk.
Moraph service team
Moraph identity engineers and service managers. Runs Imprivata on your behalf: configuration, profiles, monitoring, updates and incidents.
- Sees: Imprivata configuration, server or appliance health and agent status; Profile failures and sign-on incidents; Change requests and their approvals
- Does: Configures policies and profiles to the approved baseline; Tests and updates profiles ahead of application upgrades; Applies Imprivata updates in agreed maintenance windows; Works sign-on incidents and escalates to Imprivata where needed; Pulls sign-in records when your security officer requests them; Prepares the monthly service review
- Cannot: Change policies without an approved change request; Sign in to clinical applications as a clinician
- Approvals: Every configuration change is made against a change request approved by the owner you name.
- Notified about: Health alerts, profile failures, vendor notices, and scheduled application upgrades.
Service desk
IT service desk analyst, tier 1 support. Takes clinician calls about sign-on and badges and routes them.
- Sees: Whether a user's badge is enrolled; Known issues and planned changes
- Does: Logs sign-on and profile problems; Guides clinicians through badge re-enrollment; Routes tickets to Moraph or client IT
- Cannot: Change profiles or policies; See sign-in history
- Approvals: None; tickets are worked by Moraph or client IT.
- Notified about: Planned changes and known issues.
Auditor (read-only)
Internal auditor, compliance analyst, external assessor under temporary access. Reviews evidence of access controls without changing anything.
- Sees: Policies, the configuration baseline and change history; Administrator access reviews; Sign-in records within the scope granted
- Does: Reads and exports evidence within their scope, with each export logged; Requests further evidence through the HIPAA security officer
- Cannot: Change, approve or delete anything; Keep access after the agreed end date
- Approvals: Access is approved by the HIPAA security officer with a scope and an end date.
- Notified about: Nothing by default.
Permissions at a glance
| Action | Informatics | Client IT | Security | Badge office | Moraph team | Service desk | Auditor |
|---|---|---|---|---|---|---|---|
| Request a new application profile | Full | Full | View | – | View | – | – |
| Build and update sign-on profiles | Approves | Approves | – | – | Full | – | View |
| Change authentication policies | – | View | Approves | – | Full | – | View |
| Change timeout and lock rules | View | Approves | Approves | – | Full | – | View |
| Enroll or remove a badge | – | Full | – | Full | Full | Own work | – |
| Configure two-factor signing for EPCS | View | Approves | Approves | – | Full | – | View |
| Apply Imprivata updates | View | Approves | View | – | Full | – | – |
| View sign-in records | – | View | Full | – | Own work | – | View |
| View the configuration baseline | View | View | View | – | Full | – | View |
| Manage Imprivata administrator access | – | Approves | Approves | – | Full | – | – |
| View service reports | View | View | View | – | Full | – | View |
"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.
How access is controlled
- Moraph changes policies and profiles only against a change request approved by the owner you name, and each change is recorded with the request it came from.
- Moraph's staff pull sign-in records only when your security officer requests them, for example for an investigation, and each request is recorded.
- Imprivata administrator roles are agreed with you during onboarding and reviewed with your security officer at each access review.
- Auditors receive temporary read-only access to evidence with a defined scope and an end date, rather than shared accounts.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.