Administration
Roles and permissions in Security Awareness Training
Each role in Security Awareness Training: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Security Awareness Training 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 Security Awareness Training. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in KnowBe4 as part of the managed service.
Roles
Security program owner
Chief information security officer, information security officer, IT risk manager. Owns the awareness program, approves what is tested and taught, and reports on it to management and the board.
- Sees: All campaign results, training completions and trends; Individual results, under your institution's policy; The program calendar and change history; Monthly reviews from Moraph
- Does: Approves the annual program and each campaign's scenario; Sets the policy for repeat failures and manager follow-up; Decides which staff groups are exempt from or added to campaigns; Approves changes Moraph proposes after reviews; Presents program results to management, the board and examiners
- Cannot: Use simulation results for discipline outside the policy your institution has approved; Edit recorded results
- Approvals: Approves campaigns, scenario choices and program changes. Scenarios naming executives or partners also need the approval your policy requires.
- Notified about: Campaigns about to launch, campaign results, overdue training beyond your threshold and the monthly program review.
People manager
Branch manager, operations manager, department head. Makes sure their team completes training and follows up with people who need extra help.
- Sees: Training status for their own team; Simulation results for their team, where your policy allows; Repeat failure lists for their team
- Does: Follows up on overdue training; Discusses repeat failures with staff under your policy; Suggests scenarios based on fraud attempts their team has seen
- Cannot: See other teams' results; Exempt staff from training or campaigns
- Approvals: Exemption requests go to the security program owner.
- Notified about: Overdue training and repeat failures in their team.
Staff member
All employees and contractors in scope. Learns to spot and report fraud attempts, and completes required training.
- Sees: Their own assigned training and due dates; Feedback pages after a simulation; Their own completion history
- Does: Completes required and remedial training; Reports suspicious email with the Phish Alert Button; Acknowledges security policies where the program includes them
- Cannot: See anyone else's results; Opt out of required training
- Approvals: None.
- Notified about: Training assigned and due, and reminders from KnowBe4.
Client IT administrator
Email administrator, identity administrator, help desk lead. Keeps the technical pieces working: delivery of simulations, the reporting button, and the directory feed.
- Sees: Campaign schedules and sending details; Directory sync status; Where reported email is routed
- Does: Maintains mail allow-listing for simulations; Deploys and maintains the Phish Alert Button; Maintains directory synchronization and single sign-on; Routes real reported phishing to your security team
- Cannot: Change scenarios, groups or training assignments; See individual simulation results unless granted
- Approvals: Technical changes follow your own change process.
- Notified about: Upcoming campaigns, delivery problems and directory sync failures.
Moraph service team
Moraph awareness program specialists, service desk analysts and the named service manager. Runs the program day to day on KnowBe4 and reports on it.
- Sees: Campaign results, training status and directory data in KnowBe4; Platform notices from KnowBe4; The approved program and policies
- Does: Builds, tests, launches and closes campaigns; Adapts scenario templates to your institution; Assigns training and follows up on overdue items; Prepares campaign summaries and monthly reviews; Raises platform issues with KnowBe4 support; Assembles evidence packs on request
- Cannot: Launch a campaign that has not been approved; Use real logos of your partners or vendors without your approval; Share individual results outside the people your policy names
- Approvals: Every campaign and program change they make is approved by your security program owner first.
- Notified about: Delivery failures, directory sync errors and new service requests.
Auditor or examiner (read-only)
Internal auditor, external auditor, regulatory examiner (under temporary access). Checks that training and testing happen as the institution's program says.
- Sees: Training completion and campaign summaries; The approved program and its change history; Evidence packs within the scope granted
- Does: Reviews evidence and reports; Requests additional detail through the program owner
- Cannot: Change or delete anything
- Approvals: Their access is approved by the security program owner, with a scope and an end date.
- Notified about: Nothing by default.
Permissions at a glance
| Action | Program owner | Manager | Staff | Client IT | Moraph team | Auditor |
|---|---|---|---|---|---|---|
| Approve the annual program | Approves | – | – | – | View | View |
| Build and launch campaigns | Approves | – | – | View | Full | – |
| View all campaign results | Full | – | – | – | Full | View |
| View team results | Full | Own work | – | – | Full | – |
| Complete assigned training | Own work | Own work | Own work | Own work | – | – |
| Assign training and groups | Approves | – | – | – | Full | – |
| Approve exemptions | Approves | – | – | – | View | View |
| Maintain mail delivery and reporting button | View | – | – | Full | View | – |
| Maintain directory sync | View | – | – | Full | View | – |
| Prepare evidence packs | Full | – | – | – | Full | View |
| Manage platform users and roles | Approves | – | – | View | Full | – |
"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.
How access is controlled
- Individual results are sensitive. Who can see them, and how they may be used, follows a policy your institution approves before the first campaign; Moraph configures KnowBe4 to match it.
- Moraph launches a campaign only after your program owner approves the scenario, audience and timing, and each approval is recorded.
- Groups follow your identity provider, so access and enrollment change as people join, move and leave. Administrators and Moraph staff sign in with single sign-on and multi-factor authentication.
- Auditors, examiners and insurers' assessors can be given read-only evidence for a defined scope and period rather than platform accounts.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.