Skip to content

Administration

Roles and permissions in Digital Transaction Management

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

Applies to Digital Transaction Management 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. Loan officer or closer
  3. Lending operations owner
  4. Compliance officer
  5. Client DocuSign administrator
  6. Moraph DocuSign engineer
  7. Moraph service manager
  8. Auditor or examiner (read-only)
  9. Permissions at a glance
  10. How access is controlled

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

Roles

Loan officer or closer

Loan officer, mortgage loan originator, closer, loan processor. Sends loan documents for signature and follows them to completion.

  • Sees: Templates available to their role and branch; Envelopes they sent, or their team's envelopes where shared; Envelope status and history for their transactions
  • Does: Sends envelopes from templates or from the loan system; Fills in transaction details the template asks for; Corrects or voids their own envelopes before completion, as procedures allow; Resends reminders and answers borrower questions
  • Cannot: Create or change templates; Change signer authentication required by a template; Change the consumer disclosure or account settings
  • Approvals: None in DocuSign; loan approvals follow your own procedures before documents are sent.
  • Notified about: Envelopes viewed, signed, completed or declined, and delivery failures.

Lending operations owner

Head of loan operations, mortgage operations manager, closing manager. Owns the signing processes and templates for the institution's loan products.

  • Sees: All templates, their versions and owners; Envelope volumes and failures by product and branch; Change requests and their status
  • Does: Approves template changes and new templates; Sets which templates each role and branch can use; Signs off template testing before release; Attends the service review
  • Cannot: Approve changes to the consumer disclosure without the compliance officer; Approve a change they requested themselves where a second approver is named
  • Approvals: Approves template and process changes; changes affecting disclosures or authentication also need the compliance officer.
  • Notified about: Changes waiting for approval, templates ready for testing and integration failures.

Compliance officer

Compliance officer, consumer compliance manager, chief compliance officer. Makes sure electronic signing meets ESIGN, UETA and disclosure requirements.

  • Sees: The consumer disclosure and its version history; Authentication rules by document type; Template change history and envelope evidence
  • Does: Approves the consumer disclosure text; Approves authentication requirements by document type; Reviews template changes that affect disclosures or their timing; Requests envelope evidence for complaints, disputes and examinations
  • Cannot: Change templates or settings directly; Send or void envelopes unless also given a sender role
  • Approvals: Required approver for changes to the consumer disclosure, authentication rules and disclosure templates.
  • Notified about: Changes needing compliance review and requests for envelope evidence.

Client DocuSign administrator

IT administrator, loan systems administrator. Manages users and first-line support within the delegated scope the institution keeps.

  • Sees: Users, groups and permission profiles; Open requests and tickets
  • Does: Adds, changes and closes sender accounts, or maps them from single sign-on; Assigns users to groups and permission profiles; Handles first-line sender questions; Raises change requests
  • Cannot: Change templates, the consumer disclosure or authentication settings; Grant themselves account administrator rights
  • Approvals: User changes follow your access procedures; changes they request to templates or settings are approved by the owners.
  • Notified about: Requests they raised, planned changes and DocuSign service notices.

Moraph DocuSign engineer

Moraph DocuSign engineer, Moraph integration engineer. Builds and maintains templates, settings and integrations under approved changes, and provides second-line support.

  • Sees: Account settings, templates and integration configuration; Envelope status and errors needed to support you; Document content only where a support task needs it and you have authorized it
  • Does: Builds and changes templates and settings under approved requests; Builds and monitors integrations with your loan systems; Follows up delivery failures and integration errors; Retrieves envelope evidence on request; Raises platform issues with DocuSign support
  • Cannot: Release a change without approval; Send envelopes to your customers on your behalf; View completed documents without an authorized support reason
  • Approvals: Every change needs approval from the lending operations owner, and from the compliance officer where disclosures or authentication are affected.
  • Notified about: Approved changes, integration failures and DocuSign service notices.

Moraph service manager

Moraph service manager, client success manager. Accountable for the service: requests, escalations, reporting and the service review.

  • Sees: All tickets, change requests and escalations; Service reports and open risks
  • Does: Runs the service review and records actions; Tracks requests to closure; Coordinates with DocuSign on platform issues; Raises risks such as templates without an owner
  • Cannot: Change templates or settings; Accept a risk on your behalf
  • Approvals: None of their own; decisions go to your owners.
  • Notified about: Escalations, overdue requests and DocuSign incidents affecting you.

Auditor or examiner (read-only)

Internal auditor, external auditor, regulatory examiner (under temporary access). Reviews electronic signature evidence and controls without changing anything.

  • Sees: Envelope evidence for sampled transactions; Template versions, the consumer disclosure and change history; Evidence packs within the scope granted
  • Does: Reads evidence within their scope; Requests more evidence through the compliance officer
  • Cannot: Change, send or void anything
  • Approvals: Their access is approved by your institution with a scope and an end date.
  • Notified about: Nothing by default.

Permissions at a glance

ActionLoan officerLending opsComplianceClient adminMoraph eng.Moraph serviceAuditor
Send envelopes from templatesOwn workFull–––––
Correct or void an envelopeOwn workFull–––––
Create or change a template–ApprovesApproves–Full––
Change the consumer disclosure–ViewApproves–Full–View
Change signer authentication rules–ApprovesApproves–Full––
Change account settings–ApprovesView–Full––
Manage users and permission profiles–View–FullFull––
Configure integrations–Approves–ViewFull––
Retrieve envelope evidenceOwn workFullFull–Full–View
View change history–ViewViewViewViewViewView
Run the service review–ViewView––Full–

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

How access is controlled

  • Senders use templates; they do not build them. Template, disclosure and authentication changes are made by Moraph engineers and approved by your owners.
  • Changes to the consumer disclosure, authentication rules or disclosure templates need your compliance officer's approval as well as the lending operations owner's.
  • Moraph engineers work through named accounts with the permissions their tasks need. They do not send envelopes to your customers, and they open completed documents only for an authorized support reason.
  • Roles, groups and permission profiles are agreed during implementation; every change to them is recorded, and auditors get read-only evidence with a scope and an end date.

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.