Skip to content

Administration

Roles and permissions in Clinical Collaboration

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

Applies to Clinical Collaboration 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. Privacy officer
  3. Clinical informatics lead
  4. Client IT administrator
  5. Clinician or care team member
  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 Clinical Collaboration. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Microsoft Teams as part of the managed service.

Roles

Privacy officer

Privacy officer, HIPAA privacy officer, chief compliance officer. Decides how PHI may be handled in Teams and approves the settings and changes that affect it.

  • Sees: The approved clinical configuration baseline and its history; Change requests that affect guests, recording, retention or sharing; Drift findings and how each was resolved; Guest access and external sharing reports
  • Does: Approves the clinical baseline before it is applied; Approves or rejects changes that affect PHI handling; Decides retention periods for chats, channels and recordings with records management; Requests legal holds and privacy investigations through the service; Reviews service reports and open risks at each service review
  • Cannot: Change tenant settings directly through the Moraph service records; Approve a change they requested themselves when a second approver is required by your policy
  • Approvals: Approves the baseline and every change that touches guests, recording, transcription, retention or external sharing.
  • Notified about: Changes waiting for approval, drift findings involving PHI settings, privacy-relevant incidents, and guest access reviews coming due.

Clinical informatics lead

CMIO, CNIO, clinical informatics manager, virtual care program lead. Shapes how care teams and virtual visits use Teams so the setup fits clinical work.

  • Sees: Team and channel templates for clinical units and programs; Virtual visit meeting templates and their settings; Adoption and use reports by unit and service line
  • Does: Defines team structures and naming for clinical units; Requests new clinical teams, templates and visit types; Agrees virtual visit workflows with clinical leaders; Takes clinician feedback to service reviews; Coordinates clinician training with your education team
  • Cannot: Approve changes to guest, recording or retention settings without the privacy officer; Grant tenant administration rights
  • Approvals: Approves clinical templates and team structures; settings that affect PHI also need the privacy officer.
  • Notified about: Requests they raised moving through approval, planned changes that affect clinicians, and service review reports.

Client IT administrator

Microsoft 365 administrator, collaboration services manager, identity administrator. Owns the tenant, licenses and directory, and is the technical counterpart to Moraph's service team.

  • Sees: All Moraph change records and configuration documentation; Moraph's administrative access to the tenant and its activity; Service health, incidents and Microsoft notices affecting the service
  • Does: Grants and reviews the administrative roles Moraph uses; Manages licensing and directory groups that drive team membership; Approves technical changes and schedules them around clinical operations; Coordinates with your identity, device and network teams; Works incidents with Moraph where your systems are involved
  • Cannot: Approve changes that affect PHI handling without the privacy officer; Remove the audit records of Moraph's administrative actions
  • Approvals: Approves technical changes and Moraph's administrative access; PHI-related changes also need the privacy officer.
  • Notified about: Incidents, Microsoft notices with impact on your tenant, scheduled changes and access reviews for Moraph's roles.

Clinician or care team member

Physicians, nurses, advanced practice providers, therapists, care coordinators. Uses Teams to talk with colleagues and patients under the policies your organization approved.

  • Sees: Teams, channels and chats they are a member of; Virtual visit meetings they host or join; Files shared in their teams under the sharing rules that apply
  • Does: Chats and calls with care team members; Hosts virtual visits and admits patients from the lobby; Shares files within their teams; Raises requests and problems through your service desk
  • Cannot: Change meeting, guest, recording or retention policies; Invite guests or external participants beyond what policy allows; Delete content that a retention policy or hold requires to be kept
  • Approvals: Requests for new teams, guests or exceptions go to the owners your process names.
  • Notified about: Teams notifications they choose, and notices of planned changes that affect them.

Moraph service team

Moraph service engineer, service delivery manager, Moraph service desk. Configures, monitors and maintains the Teams environment for you, on approved requests and to the documented baseline.

  • Sees: Tenant configuration for Teams and the services it depends on; Service health, Microsoft notices and drift findings; Change, access and incident records for your service
  • Does: Applies the approved baseline and approved changes; Monitors configuration drift and service health; Handles access, guest and team requests through the approved route; Leads incident handling for the service and escalates to Microsoft; Prepares service review reports; Maintains configuration documentation
  • Cannot: Read chats, files or recordings as part of routine operations; Apply a change without the approvals your process requires
  • Approvals: Every change Moraph applies is approved by your named approvers; emergency changes are reviewed with you afterwards.
  • Notified about: Service health alerts, drift findings, new requests and approvals, and Microsoft notices that affect your configuration.

Auditor (read-only)

Internal auditor, compliance reviewer, external assessor under temporary access. Reviews evidence that Teams is configured and run as approved, without changing anything.

  • Sees: The approved baseline and its version history; Change, access review and drift records; Service review reports
  • Does: Reads and exports evidence within the scope granted; Leaves review notes where enabled
  • Cannot: Change, approve or delete anything
  • 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

ActionPrivacyInformaticsClient ITClinicianMoraph teamAuditor
Approve the clinical baselineApprovesViewApproves–ViewView
Apply tenant and Teams settings––Approves–Full–
Change guest, recording or retention policyApprovesViewApproves–Full–
Request new clinical teams or templatesFullFullFullOwn workView–
Host virtual visits–––Full––
Invite guests within policy––ViewOwn workFull–
Apply legal holdsApproves–View–Full–
Review guest access and team ownershipApprovesViewFull–FullView
View drift findingsViewViewView–FullView
View change and access recordsViewViewView–FullView
Manage Moraph's administrative accessView–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

  • Roles here describe who decides what in the service. In Teams itself, your users have ordinary Microsoft 365 roles, and Moraph's engineers hold only the administrative roles your IT team grants.
  • Moraph does not decide privacy policy. Settings that affect PHI, guests, recording, transcription or retention change only with your privacy officer's approval.
  • Moraph's administrative access is reviewed with your IT administrator and recorded with the request it served.
  • Auditors and assessors get temporary read-only access to service records with a defined scope and an end date, rather than shared accounts.

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.