Skip to content

Administration

Roles and permissions in Identity Governance

Each role in Identity Governance: what it sees, does and cannot do, its approvals, and a permissions matrix.

Applies to Identity Governance as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 4 min readReport a problem
On this page
  1. Roles
  2. Identity governance lead
  3. Privacy officer
  4. Manager or nurse manager
  5. Application owner
  6. Moraph service engineer
  7. Auditor (read-only)
  8. Permissions at a glance
  9. How access is controlled

Who can see and do what in Identity Governance. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in SailPoint as part of the managed service.

Roles

Identity governance lead

IAM manager, director of information security, CISO or delegate. Owns identity governance for the organization and makes the decisions Moraph carries out.

  • Sees: The role model, policies and connected applications; Provisioning results, exceptions and open manual tasks; Certification campaign progress and results; Moraph's change record and service reports
  • Does: Approves the role model and changes to it; Approves configuration changes requested through Moraph; Sets certification schedules and scope; Decides on escalated exceptions and policy violations; Attends monthly service reviews
  • Cannot: Approve a change they requested without a second approver your policy names; Edit Moraph's change record or SailPoint's audit history
  • Approvals: Approves role model and configuration changes, certification campaigns and policy exceptions.
  • Notified about: Changes waiting for approval, escalated violations, failed provisioning and overdue certifications.

Privacy officer

Chief privacy officer, HIPAA privacy officer, compliance officer. Makes sure access to patient information follows the minimum necessary standard.

  • Sees: Roles and the clinical access each one grants; Who holds access to sensitive record categories; Certification results for clinical applications
  • Does: Defines minimum necessary requirements for roles; Approves access to sensitive record categories; Reviews out-of-role clinical access; Requests targeted reviews after a privacy concern
  • Cannot: Change SailPoint configuration directly; Approve their own access requests
  • Approvals: Approves roles that grant broad clinical access and individual access to sensitive record categories.
  • Notified about: Requests for sensitive access and certification results showing out-of-role clinical access.

Manager or nurse manager

Nurse manager, department director, supervisor. Confirms that the people they manage have the access their work needs and no more.

  • Sees: Their staff's current access and its source, role or request; Pending requests from their staff; Their certification tasks
  • Does: Approves or denies access requests from their staff; Certifies or revokes their staff's access; Requests transition access when staff move between units; Sponsors contractors and students with end dates
  • Cannot: Approve access for themselves; See staff outside their reporting line; Change roles
  • Approvals: Their approvals are the first step; application owners and the privacy officer approve where your policy requires.
  • Notified about: Requests waiting, certification campaigns assigned and reminders, and sponsored accounts about to expire.

Application owner

EHR security analyst, application manager, department system owner. Controls who can use their application and what each entitlement allows.

  • Sees: Entitlements in their application and who holds them; Requests for their application; Manual provisioning tasks for disconnected applications
  • Does: Approves access to their application; Certifies entitlements in their application; Describes entitlements in plain language for reviewers; Completes manual provisioning and removal tasks
  • Cannot: Approve access for themselves; Change the role model without the identity governance lead
  • Approvals: Approves requests for their application after the manager.
  • Notified about: Requests waiting, manual tasks assigned and overdue removals.

Moraph service engineer

Moraph identity engineer, managed service analyst. Configures, monitors and operates SailPoint for your organization under the agreed procedures.

  • Sees: SailPoint configuration, connectors and provisioning results; Aggregation and provisioning errors; The change record and service tickets
  • Does: Builds and maintains connectors, roles, workflows and policies; Applies approved changes and records them; Monitors provisioning and aggregation and fixes failures; Follows up open manual tasks with application owners; Runs certification campaigns and carries out revocations; Prepares the monthly service review
  • Cannot: Approve access or changes on your behalf; Grant themselves access to your clinical applications; Make policy decisions or accept risk
  • Approvals: Every configuration change needs your identity governance lead's approval; emergency changes follow the agreed procedure and are reviewed afterward.
  • Notified about: Provisioning and connector failures, approved changes ready to apply and certification deadlines.

Auditor (read-only)

Internal auditor, external auditor, compliance reviewer (under temporary access). Tests access controls using the records SailPoint and Moraph keep.

  • Sees: Access history and approvals within the scope granted; Certification results; The change record
  • Does: Searches and reads records within scope; Receives exports prepared for the audit
  • Cannot: Change, approve or revoke anything
  • Approvals: Access is approved by the identity governance lead with a scope and end date.
  • Notified about: Nothing by default.

Permissions at a glance

ActionIG leadPrivacyManagerApp ownerMoraph eng.Auditor
Approve role model changesApprovesApproves–View–View
Configure SailPointApproves–––Full–
Request accessOwn workOwn workOwn workOwn work––
Approve staff access requestsFull–Own workOwn work––
Approve sensitive record accessViewApproves––––
Certify accessFullViewOwn workOwn work–View
Launch certification campaignsApproves–––Full–
Decide policy violationsApprovesApproves––ViewView
Complete manual removal tasksView––Own workFull–
View access historyViewViewOwn workOwn workViewView
Sponsor contractor accountsFull–Own work–––

"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.

How access is controlled

  • Moraph engineers operate SailPoint but never approve access or changes; every change to roles, policies or configuration is approved by your named approvers.
  • Nobody approves their own access request, and access to sensitive record categories needs the privacy officer's approval in addition to the manager's.
  • Roles in the service are agreed with you during implementation and recorded in the responsibilities for the service, including who may approve emergency changes.
  • Moraph engineers use individual named accounts with the least administrative rights the service needs, and their activity is recorded in SailPoint and in Moraph's change record.

Was this page helpful?

Report a problem with this page
What’s the problem?
Quote the step or heading if you can. Don’t include passwords or personal records.
Only if you’d like a reply. We use it for this report and nothing else.

Need help with your own setup rather than this page? Raise a support ticket.