Administration
Roles and permissions in Business Continuity Planning
Each role in Business Continuity Planning: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Business Continuity Planning 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 Business Continuity Planning. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Fusion Risk Management as part of the managed service.
Roles
Continuity program manager
Business continuity manager, operational resilience manager, BCM program lead. Owns the continuity program: sets the methodology, approves analyses and plans, and answers to management, the board and examiners.
- Sees: Every impact analysis, plan, exercise and issue across the institution; Program dashboards for plan currency, test coverage and open issues; Recovery gaps between business needs and IT capability; The service record of changes Moraph has made
- Does: Approves recovery objectives and plans; Sets the annual exercise schedule with Moraph; Assigns plan owners and review dates; Accepts or escalates exercise findings; Approves change requests to templates and workflows; Presents program reporting to committees and the board
- Cannot: Edit or delete entries in the platform's audit history; Approve a plan they wrote themselves where your policy requires a second approver; Change platform configuration directly without a logged change request
- Approvals: Approves impact analyses, plans and change requests; plans they author are approved by a second designated approver.
- Notified about: Plans and analyses overdue for review, exercise results recorded, issues past their due date, and Moraph service notices.
Plan owner
Business-line manager, department head, branch operations manager. Keeps their unit's impact analysis and continuity plan accurate and takes part in exercises.
- Sees: Their unit's impact analysis, plan and dependencies; Exercises their unit takes part in and the issues raised; Review dates and reminders for their plan
- Does: Completes and updates the impact analysis for their unit; Writes recovery procedures and names alternates; Submits the plan for approval; Records actions and results during exercises; Updates issues assigned to them
- Cannot: Approve their own plan or recovery objectives; See other units' plans unless granted; Change templates or questionnaires
- Approvals: Their analysis and plan are approved by the continuity program manager.
- Notified about: Plan and analysis reviews coming due, plans returned with comments, exercises scheduled, and issues assigned to them.
IT disaster recovery lead
IT DR manager, infrastructure manager, application recovery lead. Records what IT can actually recover and how fast, and runs the technical recovery and failover tests.
- Sees: Applications and infrastructure with their recovery objectives and recorded capability; Processes that depend on each application; Technical test records and issues
- Does: Maintains disaster recovery plans for applications and infrastructure; Records recovery capability and test timings; Runs failover and recovery tests and logs results; Owns remediation of technical findings
- Cannot: Approve business recovery objectives; Close an issue raised against their own team without the program manager's acceptance
- Approvals: Disaster recovery plans and test results are reviewed by the continuity program manager.
- Notified about: Recovery gaps where business needs exceed recorded capability, tests scheduled, and technical issues assigned to them.
Crisis management lead
Chief operating officer, crisis management team lead, incident commander. Leads the institution's response to a declared disruption and owns the crisis plan.
- Sees: Crisis and incident plans; Affected processes, dependencies and contacts during an incident; Exercise results for crisis scenarios
- Does: Approves the crisis management plan; Declares and closes incidents in the platform; Records decisions and actions during a disruption; Takes part in crisis tabletop exercises
- Cannot: Change templates or configuration; Delete incident records after the event
- Approvals: The crisis plan is approved by the crisis management lead and recorded by the program manager.
- Notified about: Incidents declared, crisis exercises scheduled, and crisis plan reviews coming due.
Auditor or examiner (read-only)
Internal auditor, external auditor, regulatory examiner (under temporary access). Reviews the program's plans, tests and issues without being able to change anything.
- Sees: Plans, analyses, exercise records and issues within the scope granted; Program dashboards and reports; Approval and review history
- Does: Searches and reads records within their scope; Exports reports they have been given access to
- Cannot: Change, approve or delete anything
- Approvals: Their access is approved by the continuity program manager, with a scope and an end date.
- Notified about: Nothing by default.
Moraph service administrator
Moraph managed-service engineer, platform administrator. Configures and administers the platform for you, under change requests your organization approves.
- Sees: Platform configuration, users, roles, imports and workflows; Program data needed to support users, under your access policy
- Does: Builds and maintains templates, questionnaires, workflows and dashboards; Runs and monitors scheduled data imports; Sets up exercises and prepares program reports; Adds and removes users on your instruction and runs access reviews; Tests platform updates against your configuration
- Cannot: Approve plans, recovery objectives or findings; Make a configuration change without an approved change request, except to restore service; Grant access that your organization has not approved
- Approvals: Configuration changes are approved by the continuity program manager; access changes follow your access request process.
- Notified about: Import failures, platform service notices, change requests raised, and access reviews coming due.
Permissions at a glance
| Action | Program mgr | Plan owner | IT recovery | Crisis lead | Auditor | Moraph admin |
|---|---|---|---|---|---|---|
| Complete an impact analysis | Full | Own work | Own work | – | – | – |
| Approve recovery objectives | Approves | – | – | – | – | – |
| Edit a continuity or DR plan | Full | Own work | Own work | Own work | – | – |
| Approve a plan | Approves | – | – | Approves | – | – |
| Record exercise results | Full | Own work | Own work | Own work | – | Full |
| Accept or close issues | Approves | Own work | Own work | – | – | – |
| Declare and manage an incident | Full | – | – | Full | – | – |
| Change templates and workflows | Approves | – | – | – | – | Full |
| Manage users and roles | Approves | – | – | – | – | Full |
| View program dashboards | Full | Own work | Own work | View | View | View |
| View audit history | 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
- Nobody approves a plan or recovery objective they wrote themselves, and Moraph administrators never approve program content; they configure the platform under your change approvals.
- Roles are set up with you during onboarding and can be limited by business line, region or location, so plan owners see their own unit's material.
- Every access change is logged, and Moraph runs periodic access reviews for your program manager to certify.
- Staff sign in through your identity provider. Auditors and examiners get temporary read-only access with a defined scope and an end date.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.