Skip to content

Administration

Roles and permissions in Secure Messaging

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

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

Last reviewed 5 min readReport a problem
On this page
  1. Roles
  2. Clinical communication owner
  3. Privacy officer
  4. Client IT administrator
  5. Unit or department scheduler
  6. Clinician
  7. Moraph service team
  8. Auditor (read-only)
  9. Permissions at a glance
  10. How access is controlled

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

Roles

Clinical communication owner

CNO or CMO delegate, director of nursing informatics, clinical communications manager. Owns how clinical messages flow: which roles exist, how routing and escalation work, and when pagers are retired.

  • Sees: Role, routing and escalation configuration; Role coverage and schedule gaps by unit; Adoption and pager retirement progress; Interface health for clinical alerts
  • Does: Approves roles, routing rules and escalation paths; Approves alert types sent to phones from lab and other systems; Decides the pager retirement plan for each unit; Brings clinician feedback to service reviews; Requests changes through the service
  • Cannot: Change retention or message lifespan without the privacy officer; Grant administrative access to TigerConnect
  • Approvals: Approves roles, routing, escalation and alert types; retention settings also need the privacy officer.
  • Notified about: Role coverage gaps, interface incidents that affect clinical alerts, changes waiting for approval, and service review reports.

Privacy officer

Privacy officer, HIPAA privacy officer, chief compliance officer. Decides how long messages are kept, who can see them and what may be sent, and approves settings that affect PHI.

  • Sees: Retention, lifespan and recall settings; Change requests that affect PHI handling; Records of message retrievals made for investigations or legal requests
  • Does: Approves retention and lifespan settings; Approves policies on attachments, images and forwarding; Requests message retrieval for investigations through the service; Reviews privacy-relevant incidents
  • Cannot: Change routing or roles; Read messages without a logged request under your process
  • Approvals: Approves retention, lifespan, attachment and export settings and any message retrieval request.
  • Notified about: Changes waiting for approval, privacy-relevant incidents, and completed retrieval requests.

Client IT administrator

Clinical systems manager, identity administrator, mobile device manager. Owns the directory, devices, network and source systems that TigerConnect depends on.

  • Sees: Directory synchronization status and errors; Interface configuration and health; Moraph's administrative access and its activity; Change and incident records
  • Does: Maintains directory attributes used for accounts and roles; Provides access to source systems for interfaces; Approves technical changes and schedules them; Manages devices and app deployment where you use mobile device management; Works incidents with Moraph where your systems are involved
  • Cannot: Approve clinical routing or retention changes on behalf of clinical or privacy owners; Remove records of Moraph's administrative actions
  • Approvals: Approves technical changes, interfaces and Moraph's administrative access.
  • Notified about: Directory sync errors, interface incidents, scheduled changes and access reviews for Moraph's roles.

Unit or department scheduler

Unit secretary, department scheduler, medical staff office coordinator. Keeps the schedules and role assignments that routing depends on accurate.

  • Sees: On-call schedules and role assignments for their unit or department; Coverage gaps flagged for their area
  • Does: Maintains schedules in your scheduling system; Corrects role assignments when coverage changes; Resolves coverage gaps flagged by the service
  • Cannot: Create new roles or change routing rules; See other departments' schedules unless granted
  • Approvals: Changes to routing or roles go to the clinical communication owner.
  • Notified about: Coverage gaps for their area and schedule import errors.

Clinician

Physicians, nurses, advanced practice providers, pharmacists, respiratory therapists. Uses the app to reach colleagues and to receive urgent messages and alerts.

  • Sees: Messages and conversations they are part of; The directory and roles they are allowed to message; Alerts routed to them or their role
  • Does: Sends and replies to messages and group conversations; Takes and hands off roles at shift change where configured; Acknowledges priority messages and alerts; Reports problems through your service desk
  • Cannot: Change retention, routing or escalation; Keep access after leaving the organization
  • Approvals: None.
  • Notified about: Messages and alerts routed to them or their role, as configured.

Moraph service team

Moraph service engineer, integration engineer, Moraph service desk. Configures, monitors and maintains TigerConnect and its interfaces to your approved design.

  • Sees: TigerConnect administrative configuration; Interface volumes, errors and logs; Directory sync status; Change, access and incident records
  • Does: Applies approved roles, routing, escalation and retention settings; Builds, tests and monitors interfaces; Handles user, role and access requests; Leads incident handling and escalates to TigerConnect; Prepares service reviews and maintains documentation
  • Cannot: Read message content as part of routine operations; Apply changes without the approvals your process requires; Decide clinical routing or retention policy
  • Approvals: Every change Moraph applies is approved by your named owners; emergency changes are reviewed with you afterwards.
  • Notified about: Interface errors, directory sync failures, new requests and approvals, and TigerConnect notices that affect your configuration.

Auditor (read-only)

Internal auditor, compliance reviewer. Reviews evidence that the service is configured and run as approved.

  • Sees: Configuration documentation and its history; Change, access review and incident records; Service review reports
  • Does: Reads and exports evidence within the scope granted; Leaves review notes where enabled
  • Cannot: Change, approve or delete anything; Read message content
  • Approvals: Their access is approved by the privacy officer or IT administrator, with a scope and an end date.
  • Notified about: Nothing by default.

Permissions at a glance

ActionComms ownerPrivacyClient ITSchedulerClinicianMoraph teamAuditor
Define roles and routingApprovesViewView––FullView
Change escalation rulesApproves–View––FullView
Set retention and message lifespanViewApprovesView––FullView
Approve alert types sent to phonesApprovesViewApproves––FullView
Maintain on-call schedulesView––Own work–View–
Send and receive messagesFullFullFullFullFull––
Build and change interfacesApproves–Approves––FullView
Retrieve messages for an investigation–Approves–––Full–
Manage users and accounts––Approves––FullView
View change and incident recordsViewViewView––FullView
Manage Moraph's administrative access–ViewFull–––View

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

How access is controlled

  • Roles here describe who decides what in the service. Inside TigerConnect, clinicians hold ordinary user accounts and Moraph's engineers hold only the administrative rights your IT team grants.
  • Clinical routing is a clinical decision. Moraph configures roles, routing and escalation, but your clinical communication owner approves them.
  • Message content is retrieved only on a request approved by your privacy officer, and each retrieval is recorded with who asked, who approved and who carried it out.
  • Moraph's administrative access is reviewed with your IT administrator and recorded.

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.