Skip to content

Administration

Roles and permissions in Nuclear Command & Control (NC3) Assurance Check

Each role in Nuclear Command & Control (NC3) Assurance Check: what it sees, does and cannot do, its approvals, and a permissions matrix.

Applies to Nuclear Command & Control (NC3) Assurance Check 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. Viewer
  3. User
  4. Product administrator
  5. Permissions at a glance
  6. How access is controlled

Who can see and do what in Nuclear Command & Control (NC3) Assurance Check. Your organization's administrators and technical leads give each person one of the roles below in the Moraph Portal under People and access. Each time someone's product access is given, changed or removed, it is recorded in the product's Activity.

Roles

Viewer

Inspectors, auditors and assessors who review the evidence. Reviews the assurance record without changing it.

  • Sees: Every system, checklist, baseline, check result, discrepancy, deviation and certification in the workspace; The assurance status, schedule, baseline register, certifications and evidence packages
  • Does: Reads and prints evidence packages and the reports
  • Cannot: Record checks, open or work discrepancies, or prepare, verify or approve baselines; Change the assurance settings or the workspace settings
  • Approvals: None.
  • Notified about: Nothing by email.

User

Assurance operators, configuration managers and cybersecurity analysts. Does the day-to-day assurance work: checks, baselines, discrepancies and change records.

  • Sees: Every record in the workspace; Their own tasks and the rest of the team's
  • Does: Records check results and test results, which can't be changed once recorded; Prepares baselines and verifies baselines someone else prepared; Reviews check results someone else recorded, accepting them or sending them back with a note; Opens and investigates discrepancies, records corrective actions and proposes closure; Requests deviations and sends certifications for review
  • Cannot: Verify a baseline they prepared, or review a check result they recorded; Approve or reject a baseline, approve or dismiss a discrepancy's closure, or reopen a closed discrepancy; Decide a deviation or a certification, approve an evidence package, or mark a check result Entered in error; Change the assurance settings or the workspace settings
  • Approvals: None.
  • Notified about: When a record or task is assigned to them, and when work assigned to them is due soon or overdue; when a check result they recorded is sent back on review, a baseline they prepared is rejected, a closure they proposed is sent back, or a deviation or certification they requested is decided; when a check on a system assigned to them needs attention. The daily reminders (checks coming due, corrective actions due, baselines and closures waiting, certifications expiring) arrive as tasks.

Product administrator

The ISSM or approving authority. Everything a User can do, plus the approvals and the assurance settings.

  • Sees: Every record in the workspace; The assurance settings and the workspace settings; Recently deleted records
  • Does: Approves or rejects baselines that another person prepared and a third verified; Approves a discrepancy's closure or returns it, dismisses a discrepancy as not a discrepancy, and reopens closed ones; Approves, refuses or withdraws deviations, and certifies systems, declines or withdraws certifications; Approves evidence packages and marks check results Entered in error with a reason; Sets corrective action days by severity, reminder lead times and the certification rules; Changes the workspace's record types, fields and workflow stages, manages Work API keys and restores deleted records
  • Cannot: Give people access to the product or change their roles: your organization's administrators and technical leads do that in the Moraph Portal under People and access; Approve a baseline they prepared or verified; Approve or dismiss a discrepancy they investigated, or approve a closure they proposed; Decide a certification they sent for review or a deviation they requested or changed, or mark a result they recorded Entered in error
  • Approvals: Approves baselines, discrepancy closures, deviations and certifications, but never their own work: not a baseline they prepared or verified, a discrepancy they investigated or proposed closing, a deviation they requested or changed, or a certification they sent for review.
  • Notified about: When a record or task is assigned to them, and when work assigned to them is due soon or overdue; when a check result they recorded is sent back on review, a baseline they prepared is rejected, a closure they proposed is sent back, or a deviation or certification they requested is decided; when a check on a system assigned to them needs attention. The daily reminders (checks coming due, corrective actions due, baselines and closures waiting, certifications expiring) arrive as tasks. Product administrators are also told when a discrepancy is marked as suspected tampering, when a system stays unverified past the set days, and when a corrective action is overdue past the escalation days.

Permissions at a glance

ActionViewerUserProduct administrator
See every record, report and evidence packageFullFullFull
Record check and test results–FullFull
Prepare a baseline–FullFull
Verify a baseline (not one you prepared)–ApprovesApproves
Approve a baseline (not one you prepared or verified)––Approves
Review a check result (not one you recorded)–ApprovesApproves
Open and investigate a discrepancy and propose its closure–FullFull
Approve a discrepancy's closure (not one you investigated or proposed closing)––Approves
Decide a deviation or a certification (not one you requested or sent for review)––Approves
Mark a check result Entered in error (not one you recorded)––Full
Change the assurance settings and the workspace settings––Full
Restore deleted records––Full
Give people access and roles (in the Moraph Portal, by your organization's administrators and technical leads)–––

"Approves" means the role signs off the action.

How access is controlled

  • Two-person control is built in: a baseline is prepared by one person, verified by another and approved by a product administrator who did neither; nobody approves the closure of a discrepancy they investigated or proposed closing; and nobody decides a certification they sent for review.
  • Nobody can change a recorded check result or mark an unverified system as passing; a product administrator who didn't record it can only mark it Entered in error, with a reason.
  • Roles are given to each person by your organization's administrators and technical leads in the Moraph Portal under People and access; access isn't limited by site, system or operations center.
  • Each time someone's product access is given, changed or removed, it is recorded in the product's Activity.

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.