Skip to content

Administration

Roles and permissions in Policy Management

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

Applies to Policy Management 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. Staff member
  3. Policy owner
  4. Approver
  5. Policy coordinator
  6. Moraph service team
  7. Auditor (read-only)
  8. Permissions at a glance
  9. How access is controlled

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

Roles

Staff member

Any employee, contractor or medical staff member. Finds and follows the current version of the policies that apply to their work.

  • Sees: Current approved policies for their facility and system-wide; Attestations assigned to them; Their own attestation history
  • Does: Searches and reads policies; Acknowledges policies sent for attestation; Sends feedback on a policy to its owner where enabled
  • Cannot: See drafts or archived versions; Edit or approve a policy
  • Approvals: Nothing they do needs approval.
  • Notified about: Attestations assigned to them and reminders when they are outstanding.

Policy owner

Department director, nurse manager, pharmacy director, infection prevention lead. Keeps the policies they own accurate, current and reviewed on time.

  • Sees: Their policies in every state: draft, in approval, published and archived; Review dates and comments from approvers; Attestation progress for their policies
  • Does: Drafts new policies and revisions; Submits drafts into their approval route; Responds to approver comments; Completes scheduled reviews or starts a revision; Requests attestation for a changed policy
  • Cannot: Publish a policy without completing its approval route; Approve their own policy; Delete an archived version
  • Approvals: Every new policy and revision goes through the approval route your governance sets.
  • Notified about: Reviews coming due and overdue, policies returned with comments, and approvals completed.

Approver

Executive sponsor, committee chair, medical executive committee, chief nursing officer. Decides whether a policy is approved for use.

  • Sees: Policies waiting for their approval, with changes from the previous version; Policies they have approved before; Comments from earlier approvers in the route
  • Does: Approves or returns a policy with comments; Records committee approval with the meeting date; Delegates approval during absence where your rules allow
  • Cannot: Approve a policy they own or drafted; Edit a draft directly while approving it; Skip a step earlier in the route
  • Approvals: Their decisions are the approvals; delegation follows your governance rules.
  • Notified about: Policies waiting for their approval and reminders when they are waiting longer than your rules set.

Policy coordinator

Policy coordinator, accreditation manager, regulatory readiness manager, quality director. Runs the policy program and is the main contact for Moraph.

  • Sees: Every policy in every state; Review and approval status across the organization; Attestation campaigns and their progress; The audit trail
  • Does: Assigns owners and review intervals; Approves changes to approval routes and templates raised with Moraph; Runs attestation campaigns; Follows up overdue reviews with owners and leaders; Prepares survey evidence with Moraph
  • Cannot: Approve policies in place of the designated approvers; Edit the audit trail or delete version history
  • Approvals: Approves configuration changes; route changes for clinical policies are agreed with the medical staff office.
  • Notified about: Overdue reviews, stalled approvals, attestation progress and change requests needing a decision.

Moraph service team

Moraph platform administrator, migration specialist, service manager. Configures and runs the platform under your change approvals.

  • Sees: Configuration, routes, templates and user roles; Policy metadata and status needed to run the service; Platform notices from RLDatix
  • Does: Migrates documents and applies templates; Configures approval routes, review intervals and attestation campaigns; Connects and maintains single sign-on; Investigates access and configuration problems; Prepares the monthly service review and evidence reports
  • Cannot: Approve or publish policies; Change routes or roles without your approval; Access the platform outside the scope your organization authorizes
  • Approvals: Configuration changes are approved by the policy coordinator before they are applied.
  • Notified about: Approved change requests, access problems reported by staff and platform service notices.

Auditor (read-only)

Internal auditor, compliance reviewer, surveyor support under temporary access. Reviews policies and their governance without changing anything.

  • Sees: Policies and their version history within the scope granted; Approval records and attestation results; Review status reports
  • Does: Searches and reads policies and history; Exports evidence within scope, with each export logged; Records review notes where enabled
  • Cannot: Change, approve or archive anything
  • Approvals: Access is approved by the policy coordinator or compliance officer, with a scope and an end date.
  • Notified about: Nothing by default.

Permissions at a glance

ActionStaffOwnerApproverCoordinatorMoraphAuditor
Read current policiesFullFullFullFullViewView
Complete attestationsOwn workOwn workOwn workOwn work––
Draft and revise policies–Own work–Full––
Approve a policy––Approves–––
Publish an approved policy–––Full––
View drafts and archived versions–Own workOwn workFullViewView
Run attestation campaigns–Own work–FullFull–
Set owners and review intervals–––FullFull–
Change approval routes and templates–––ApprovesFull–
Migrate and import documents–––ApprovesFull–
Manage users and roles–––ApprovesFull–
View audit trail–––ViewViewView

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

How access is controlled

  • Nobody approves a policy they own or drafted, and a policy cannot be published until every step in its route is complete.
  • Approval routes, review intervals and roles are set with you during implementation and follow your governance documents; Moraph changes them only through approved change requests.
  • Staff need no editing account to read policies: they reach the library through single sign-on or a link from your intranet.
  • Moraph staff work under named accounts within the scope your organization authorizes, and every configuration change they make is recorded and reported in the monthly service review.

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.