Administration
Roles and permissions in Identity Access Management
Each role in Identity Access Management: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Identity Access Management 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 Identity Access Management. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in Okta as part of the managed service.
Roles
Information security officer
CISO, information security officer, ISO, head of IT risk. Owns identity and access policy for the institution and decides how authentication strength follows the risk assessment.
- Sees: The configuration baseline and its link to the risk assessment; MFA coverage, open exceptions and their review dates; Escalated security events and Moraph's recommendations; Change history, access review results and service reports
- Does: Approves the configuration baseline and changes to it; Approves or rejects MFA and policy exceptions; Decides on escalated security events, such as suspending an account; Sets the schedule and scope of access reviews; Attends the service review and accepts or challenges the open risks; Requests evidence packs for audits and examinations
- Cannot: Approve a change they requested themselves, where a second approver is named; Edit or delete the change history or the Okta System Log
- Approvals: Approves baseline changes, policy changes and exceptions; changes they request themselves are approved by a second named approver.
- Notified about: Changes waiting for approval, escalated security events, exceptions reaching their review date and access reviews overdue.
IT administrator
IT manager, systems administrator, help desk lead. The institution's day-to-day contact for the service, handling first-line user issues and requesting changes.
- Sees: Users, groups and application assignments in Okta, within the delegated admin scope agreed; Open change requests and their status; Service tickets and their history
- Does: Raises change requests and application onboarding requests; Resets authenticators and unlocks accounts after verifying the user, following the agreed procedure; Answers first-line user questions about sign-in and enrollment; Provides application details and test accounts for onboarding; Confirms changes work after Moraph applies them
- Cannot: Change authentication policies, the baseline or administrator roles; Approve their own change requests or exceptions; Grant themselves additional Okta administrator rights
- Approvals: Change requests they raise are approved by the information security officer or another named approver before Moraph applies them.
- Notified about: Updates on their requests and tickets, planned changes and Okta maintenance notices that affect users.
Application owner
Business application owner, system owner, department head. Accountable for who has access to their application and at what level.
- Sees: Users and groups assigned to their application; Access review tasks for their application; Requests for access to their application
- Does: Approves or declines requests for access to their application; Completes access reviews, confirming or removing each user's access; States the risk level of their application for the baseline; Tests single sign-on and provisioning when their application is onboarded
- Cannot: Change authentication policies or Okta configuration; Review access for applications they do not own; Approve exceptions to the baseline
- Approvals: Their review decisions are carried out by Moraph or by provisioning in Okta; removals do not need further approval.
- Notified about: Access requests for their application and access reviews assigned to them, with reminders when overdue.
Moraph identity engineer
Moraph identity engineer, Moraph platform engineer. Configures, changes and maintains the Okta tenant on the institution's behalf, under approved change requests.
- Sees: Okta configuration, policies, applications and the System Log for the client tenant; Approved change requests and the baseline; Monitoring alerts raised for the tenant
- Does: Applies approved configuration changes and records what was changed; Connects new applications for single sign-on and provisioning; Triages monitoring alerts and prepares escalations with a recommendation; Reviews Okta release notes and plans relevant changes with the client; Prepares configuration evidence for service reviews and audits
- Cannot: Make a configuration change without an approved change request, except an emergency action the agreed procedure allows, which is reported straight away; Approve exceptions or changes to the baseline; Sign in to the institution's business applications as a user
- Approvals: Every change they make needs the client's approval first; emergency actions under the agreed procedure are reviewed with the client afterwards.
- Notified about: Approved changes ready to apply, monitoring alerts and Okta service notices.
Moraph service manager
Moraph service manager, client success manager. Accountable for the service as a whole: requests, escalations, reporting and the regular service review.
- Sees: All tickets, change requests and escalations for the client; Service reports, MFA coverage and open exceptions; Open risks and actions from earlier service reviews
- Does: Runs the service review and records the actions agreed; Tracks requests and escalations to closure; Coordinates with Okta support on platform issues; Prepares evidence packs requested by the client; Raises risks, such as exceptions past their review date, with the client
- Cannot: Change the Okta configuration; Accept a risk on the client's behalf
- Approvals: None of their own; decisions they raise go to the information security officer.
- Notified about: Escalations, overdue requests and Okta incidents affecting the client.
Auditor or examiner (read-only)
Internal auditor, external auditor, regulatory examiner (under temporary access). Reviews the identity controls and their evidence without being able to change anything.
- Sees: The configuration baseline, policy settings and exception register; Access review results and change history; Evidence packs prepared for the period under review
- Does: Reads the evidence provided within their scope; Requests additional evidence through the information security officer
- Cannot: Change configuration, approve anything or see records outside their scope
- Approvals: Their access is approved by the information security officer, with a scope and an end date.
- Notified about: Nothing by default; access granted and expiring is confirmed to the person who approved it.
Permissions at a glance
| Action | Security lead | IT admin | App owner | Moraph eng. | Moraph service | Auditor |
|---|---|---|---|---|---|---|
| Approve the configuration baseline | Approves | – | – | – | – | View |
| Request a configuration change | Full | Full | Own work | – | – | – |
| Apply a configuration change | Approves | – | – | Full | – | – |
| Change authentication policies | Approves | – | – | Full | – | – |
| Approve an MFA or policy exception | Approves | – | – | – | View | View |
| Reset a user's authenticators | View | Full | – | Full | – | – |
| Assign users to an application | View | Full | Approves | Full | – | – |
| Complete an access review | View | – | Own work | – | View | View |
| Decide on an escalated security event | Full | View | – | View | View | – |
| Grant Okta administrator roles | Approves | – | – | Full | – | – |
| View change history and System Log | 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
- Moraph engineers apply changes; your institution approves them. Nobody approves a change or exception they requested themselves when a second approver is named.
- Moraph staff use named, individual administrator accounts in your Okta tenant with only the admin roles the service needs, protected by phishing-resistant MFA. There are no shared administrator accounts.
- Roles and delegated administration are agreed during implementation. Your IT team can keep first-line tasks such as authenticator resets, or hand them to Moraph.
- Every administrator action is recorded in Okta's System Log, and every change is linked to its request and approval in Moraph's change record. Auditors and examiners get read-only evidence with a defined scope and 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.