Skip to content

Administration

Roles and permissions in Mission Planning Workflow

Each role in Mission Planning Workflow: what it sees, does and cannot do, its approvals, and a permissions matrix.

Applies to Mission Planning Workflow as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.

Last reviewed 4 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 Mission Planning Workflow. 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

People who read plans and carry approved packages without changing them, such as subordinate leaders, after-action reviewers and inspectors. Sees the workspace without changing it.

  • Sees: Every plan, phase, checklist item, resource, movement leg, review and other record in the workspace; Readiness checks, plan history, reports and export packages; Tasks and progress across the workspace
  • Does: Downloads export packages (JSON and printable HTML); Checks a package file or fingerprint against the approved package
  • Cannot: Add, change or move records; Export lists or plan history as CSV files; Import packages or record who received a package; See or change Planning settings
  • Approvals: None.
  • Notified about: Nothing from the product by default.

User

Operations and logistics planners, staff reviewers, and commanders named as approvers. Does the day-to-day work: tasks, records and workflow steps.

  • Sees: Every record in the workspace; Readiness checks, plan history, reports and export packages; Their own planning work and tasks, and the rest of the team's
  • Does: Builds plans from phases, checklist items, resources, movement legs, risks, decision points, communications lines and the other record types, and sends them for review; Answers reviews, records checklist progress and scores courses of action; Copies plans and templates, starts a new version of an approved plan, and imports packages as new draft plans; Downloads packages, records who received them and exports lists and plan history as CSV files; Approves plans or returns them for changes when Planning settings name them as an approver
  • Cannot: Approve or return a plan unless Planning settings name them as an approver; Approve a plan they created; Change an approved version: changes start a new version; Accept a risk at or above the level Planning settings set for acceptance unless they are a plan approver (no level is set by default); See or change Planning settings
  • Approvals: Approves a plan version or returns it only when Planning settings name them as an approver, and never a plan they created; approving over a reviewer's non-concurrence needs a note.
  • Notified about: When a record or task is assigned to them, and when work assigned to them is due soon or overdue. Also when a plan they own or created is approved or returned, and, when named as an approver, when a plan enters review.

Product administrator

The people who run the product for your organization, such as planning administrators. Everything a User can do, plus the product's settings and reference data.

  • Sees: Every record in the workspace; Planning settings and the workspace settings; Recently deleted records
  • Does: Approves plans or returns them for changes when Planning settings name no approvers; Sets Planning settings: approvers, review areas and answered reviews needed, resource, sustainment, risk and communications rules for approval, export marking, planning factors, checklist sets and reminder periods; Adds newer record types, changes the workspace's record types, fields and workflow stages, 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 plan they created; Approve or return plans when Planning settings name approvers and they aren't one of them; Change an approved version: changes start a new version
  • Approvals: Approves a plan version or returns it when Planning settings name no approvers or name them as one, never a plan they created; approving over a reviewer's non-concurrence needs a note.
  • Notified about: When a record or task is assigned to them, and when work assigned to them is due soon or overdue. Also when a plan enters review while they are an approver.

Permissions at a glance

ActionViewerUserProduct administrator
See every plan, its readiness, history and reportsFullFullFull
Download export packages and check a package against the approved oneFullFullFull
Export lists and plan history as CSV files–FullFull
Build plans and their records, and send a plan for review–FullFull
Answer reviews and record checklist progress–FullFull
Start a new version, copy plans and import packages–FullFull
Approve a plan version or return it (approvers named in Planning settings, otherwise product administrators; never a plan they created)–ApprovesApproves
Accept a risk at the level Planning settings require before approval (plan approvers only; off by default)–ApprovesApproves
See and change Planning 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

  • Rules the product enforces: a plan enters review only with every phase and movement leg ready; it is approved only through Approve or return, by an approver who didn't create it, once required checklist items, answered reviews and the other checks Planning settings ask for are met; and an approved version is locked, so changes start a new version that goes back for approval.
  • Approvers are the people Planning settings name, who can hold the User or Product administrator role; when nobody is named, product administrators approve.
  • Access isn't limited by unit: everyone with access sees every plan in the product.
  • Roles are given to each person by your organization's administrators and technical leads 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.

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.