Skip to content

Administration

Roles and permissions in Communication Archiving

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

Applies to Communication Archiving 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. Chief compliance officer
  3. Supervisory reviewer
  4. Records and legal
  5. Client IT administrator
  6. Moraph service team
  7. Auditor or examiner (read-only)
  8. Permissions at a glance
  9. How access is controlled

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

Roles

Chief compliance officer

Chief compliance officer, head of compliance, designated supervisory principal. Owns the firm's communication archiving and supervision program and answers for it to regulators.

  • Sees: Capture coverage by channel and user, and every gap incident; Supervision policies, review backlog and policy hit rates; The configuration baseline and change history; Monthly service reviews from Moraph
  • Does: Approves which communication channels may be used for business; Approves supervision policies, lexicons and sampling rates; Approves changes to supervision configuration requested by the business or proposed by Moraph; Assigns reviewers to review groups; Receives and signs off gap incident reports; Prepares exam and board reporting on the program
  • Cannot: Delete or alter archived messages; retention storage does not allow it; Release a legal hold without the legal team's instruction
  • Approvals: Approves policy and channel changes. Changes that reduce retention also need the records owner.
  • Notified about: Capture gap incidents, supervision backlog beyond the level your procedures set, change requests awaiting approval, and the monthly service review.

Supervisory reviewer

Registered principal, compliance analyst, supervision analyst. Reviews communications that Smarsh flags or samples, and records whether each needs action.

  • Sees: Flagged and sampled messages for the review groups assigned to them; The policy or lexicon term that flagged each message; Earlier review decisions on the same conversation
  • Does: Reviews flagged messages and records a decision and comment; Escalates messages that need further action; Reports false-positive patterns for policy tuning; Requests additional searches through compliance
  • Cannot: Review their own communications; Change policies, lexicons or review groups; Export messages outside a logged production
  • Approvals: Escalations go to the chief compliance officer or the supervisor your procedures name.
  • Notified about: New items in their review queue and items returned to them.

Records manager, in-house counsel, legal operations, eDiscovery specialist. Owns retention periods and legal holds, and handles document requests from regulators and litigants.

  • Sees: Retention policies and their mapping to your retention schedule; Active legal holds and the custodians they cover; Production history with search criteria and exports
  • Does: Approves retention policy changes; Instructs Moraph to place, extend or release legal holds; Searches the archive and exports productions; Requests Moraph help with large or complex productions
  • Cannot: Shorten retention below the period the rules require; Delete messages under hold or within their retention period
  • Approvals: Their retention changes are applied by Moraph only after a recorded approval; reductions also go to the chief compliance officer.
  • Notified about: Holds placed or released, productions completed, and retention changes awaiting their approval.

Client IT administrator

Messaging administrator, Microsoft 365 or Google Workspace administrator, mobile device administrator. Owns the email, collaboration and mobile systems that Smarsh captures, and grants the technical access capture needs.

  • Sees: Connector status and the technical access each connector uses; Capture gap incidents caused by changes on their systems; Change requests that touch their systems
  • Does: Grants and maintains the service accounts and permissions connectors need; Tells Moraph in advance about changes to messaging systems; Fixes source-side causes of capture gaps with Moraph; Keeps user directory data accurate so coverage follows the population
  • Cannot: Change retention, holds or supervision policies; Read archived messages unless granted a compliance role
  • Approvals: Technical access requests from Moraph are approved by them; changes to their systems follow your own change process.
  • Notified about: Connector failures and capture gaps traced to their systems, and planned connector changes.

Moraph service team

Moraph service engineers, service desk analysts and the named service manager. Configures, monitors and maintains Smarsh for you, and reports on how the service is running.

  • Sees: Connector health, capture volumes and platform alerts; Configuration of channels, retention, holds and policies; Message content only when your compliance team asks them to run a search or production
  • Does: Configures and maintains capture connectors; Runs daily capture checks and investigates gaps; Applies approved changes to retention, holds and policies; Raises and follows platform issues with Smarsh support; Prepares the monthly service review and quarterly baseline review; Runs searches and exports at your instruction
  • Cannot: Change retention, holds or supervision policies without your recorded approval; Make supervisory decisions on messages; Read message content outside a request you have logged
  • Approvals: Every configuration change they make is tied to a change request approved by the owner you name.
  • Notified about: Platform alerts, connector failures, capture volume drops and new service requests.

Auditor or examiner (read-only)

Internal auditor, external auditor, regulatory examiner (under temporary access). Checks that capture, retention and supervision work as the firm's procedures say.

  • Sees: Capture coverage and gap incidents; Retention configuration and change history; Supervision review records within the scope granted
  • Does: Reads evidence packs and reports; Requests specific searches through compliance; Leaves review notes where the firm enables them
  • Cannot: Change, approve or delete anything
  • Approvals: Their access is approved by the chief compliance officer, with a scope and an end date.
  • Notified about: Nothing by default.

Permissions at a glance

ActionCCOReviewerRecords/legalClient ITMoraph teamAuditor
Approve channels for business useApproves–ViewViewViewView
Configure capture connectorsView––ApprovesFull–
Review flagged messagesFullOwn work–––View
Change supervision policiesApproves–––FullView
Change retention policiesApproves–Approves–FullView
Place or release legal holdsView–Approves–Full–
Search and export productionsFull–Full–Own work–
Investigate capture gapsView–ViewFullFullView
View configuration baselineView–ViewViewFullView
Manage review groups and usersApproves––ViewFull–
View service reportsView–ViewViewFullView

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

How access is controlled

  • Moraph applies changes to retention, holds and supervision policies only against a change request approved by the owner you name, and each change is recorded with the request it came from.
  • Moraph staff do not read message content as part of routine operations. They search or export only when your compliance or legal team logs a request, and each search is recorded.
  • Roles and review groups are agreed with you during onboarding and can follow your identity provider's groups. Reviewers are kept out of review groups that would cover their own communications.
  • Auditors and examiners receive temporary read-only access with a defined scope and an end date, approved by your chief compliance officer, 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.