Administration
Roles and permissions in CRM for Finance
Each role in CRM for Finance: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to CRM for Finance as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.
On this page
Who can see and do what in CRM for Finance. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Salesforce FinServ Cloud as part of the managed service.
Roles
Relationship manager or advisor
Relationship manager, financial advisor, banker, client service associate. Uses the CRM to manage client relationships, referrals and tasks.
- Sees: Clients, households and financial accounts within their book or team, as sharing rules allow; Encrypted fields their permission set allows, shown in clear to them; Their tasks, referrals and action plans
- Does: Records client interactions, notes and opportunities; Creates and works referrals; Completes action plan tasks for onboarding and reviews; Raises support requests
- Cannot: See clients outside their sharing scope; Export reports containing encrypted fields unless their role allows it; Change configuration or permissions
- Approvals: None in the CRM itself; business approvals follow your own procedures.
- Notified about: Referrals and tasks assigned to them, and planned changes that affect how they work.
Client CRM owner
Head of CRM, business systems owner, Salesforce product owner. Owns the CRM for the business and decides what changes and in what order.
- Sees: The change backlog, releases and their status; Adoption and data quality reports; Service reports and open risks
- Does: Approves or rejects change requests; Sets priorities for the backlog; Signs off user acceptance testing for releases; Approves permission set and sharing changes with the security team; Attends the service review
- Cannot: Approve key actions; that belongs to the key custodian; Approve a change they raised themselves where a second approver is named
- Approvals: Approves changes and releases; permission changes affecting encrypted data also need the information security officer.
- Notified about: Changes waiting for approval, releases ready for testing and Salesforce release dates.
Key custodian
Information security officer, head of cryptography, IT risk manager. Holds your institution's authority over the Shield keys that protect your data.
- Sees: The key inventory: which key material exists, its status and rotation history; The encryption scope: which fields and files are encrypted; The key action log
- Does: Approves key generation, rotation, revocation and destruction; Sets the rotation schedule; Requests key action records for audits; Decides with the CRM owner on changes to encryption scope
- Cannot: Carry out key actions in Salesforce directly unless that is agreed; Approve a key action they requested without a second approver
- Approvals: Every key action needs their approval; destruction of key material needs a second named approver at your institution.
- Notified about: Key actions requested and rotations due.
Compliance officer
Compliance officer, privacy officer, chief compliance officer. Makes sure access to client information, retention and records meet your obligations.
- Sees: Access reports and permission review results; Field history and event monitoring reports where licensed; Retention settings and the change history
- Does: Reviews who can see nonpublic personal information; Sets retention requirements for field history and records; Requests evidence for examinations and audits; Raises concerns and changes through the CRM owner
- Cannot: Change configuration or permissions directly; Approve key actions
- Approvals: Consulted on changes that affect client data handling; their sign-off can be made a required step for those changes.
- Notified about: Changes affecting sensitive data, escalated access events and completed access reviews.
Moraph Salesforce engineer
Moraph Salesforce engineer, Moraph CRM administrator. Builds, tests and deploys approved changes and provides second-line support.
- Sees: Org configuration, metadata and sandboxes; Approved change requests and the release plan; Client data only where a support task needs it and your institution has authorized it
- Does: Builds changes in sandboxes and deploys them through recorded releases; Tests Salesforce seasonal releases in a preview sandbox; Maintains profiles, permission sets and sharing rules under approved changes; Handles second-line support and raises platform issues with Salesforce; Prepares service and access reports
- Cannot: Deploy to production without an approved change; Carry out key actions; Grant themselves access to encrypted data
- Approvals: Every production deployment needs the CRM owner's approval; access to client data for support needs your authorization.
- Notified about: Approved changes, support requests and Salesforce release and incident notices.
Moraph encryption administrator
Moraph Salesforce engineer, Moraph security engineer. Carries out approved key actions in Shield's key management.
- Sees: Shield key status and rotation history; Key metadata and the key action log; Approved key action requests
- Does: Tracks rotation dates against the approved schedule; Carries out approved key actions; Records every key action with requester, approver and time; Prepares key action records
- Cannot: Act on keys without your key custodian's approval; Sign in to the Salesforce org or read client data; Export keys without your key custodian's approval
- Approvals: Every key action needs the key custodian's approval.
- Notified about: Approved key actions and rotations due.
Auditor or examiner (read-only)
Internal auditor, external auditor, regulatory examiner (under temporary access). Reviews controls over client data, keys and changes without being able to change anything.
- Sees: Key action records and the key action log; Access review results and change history; Evidence packs within the scope granted
- Does: Reads evidence within their scope; Requests more evidence through your compliance officer or CRM owner
- Cannot: Change anything or see client records unless your institution grants that separately
- Approvals: Their access is approved by your institution with a scope and an end date.
- Notified about: Nothing by default.
Permissions at a glance
| Action | Advisor | CRM owner | Key custodian | Compliance | Moraph eng. | Moraph encr. | Auditor |
|---|---|---|---|---|---|---|---|
| Work client records | Own work | View | – | View | – | – | – |
| View encrypted fields in clear | Own work | View | – | View | – | – | – |
| Request a change | Own work | Full | Full | Full | – | – | – |
| Approve a change or release | – | Approves | – | View | – | – | – |
| Deploy to production | – | Approves | – | – | Full | – | – |
| Change permissions and sharing | – | Approves | – | View | Full | – | – |
| Change encryption scope | – | Approves | Approves | View | Full | – | – |
| Approve a key action | – | – | Approves | – | – | – | – |
| Carry out a key action | – | – | Approves | – | – | Full | – |
| View key action log | – | – | View | View | – | View | View |
| View change history | – | View | View | View | View | – | View |
"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.
How access is controlled
- Key actions are kept separate from other administration of your org and are carried out only by the people named for them.
- No key action happens without your key custodian's approval, and destroying a key needs a second approver at your institution.
- Moraph engineers work in your org through named accounts with the permissions their tasks need. Access to client data for support is authorized by you and recorded.
- Roles, profiles and permission sets are designed with you during implementation and reviewed periodically; every change to them goes through change control and is recorded.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.