Skip to content

Administration

Roles and permissions in Mission Partner Environment (MPE) Builder

Each role in Mission Partner Environment (MPE) Builder: what it sees, does and cannot do, its approvals, and a permissions matrix.

Applies to Mission Partner Environment (MPE) Builder 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. Mission owner
  3. Foreign disclosure officer
  4. ISSM
  5. Partner administrator
  6. Moraph service manager
  7. Moraph enclave engineer
  8. Assessor or inspector (read-only)
  9. Permissions at a glance
  10. How access is controlled

Who can see and do what in Mission Partner Environment (MPE) Builder. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in the platform vendor as part of the managed service.

Roles

Mission owner

J6 or communications planner, mission commander's staff officer, program lead. Requests the enclave for a mission, names the partners and users, and decides when the mission ends.

  • Sees: Their mission's enclave, partners and users; Request, build and change status; Access reviews for their enclave; Teardown status and evidence
  • Does: Submits enclave requests with partners, users and mission period; Requests changes during the mission; Confirms partner users are still needed during access reviews; Confirms the end of the mission and lists the records to keep
  • Cannot: Approve disclosure to a partner; Approve the template or build; Extend an enclave past its end date without a recorded approval
  • Approvals: Their requests need a disclosure decision from the foreign disclosure officer and approval from the ISSM.
  • Notified about: Request and build status, end dates approaching, access reviews due and teardown complete.

Foreign disclosure officer

Foreign disclosure officer, foreign disclosure representative. Decides what categories of information each partner may receive, and keeps that decision linked to the enclave.

  • Sees: Requests naming partners; Disclosure decisions recorded for each enclave; Sharing rules configured from those decisions; Data movement records by partner
  • Does: Records the disclosure decision for each partner or references an existing one; Approves or returns sharing rules; Reviews data movement records; Withdraws a decision, which triggers the sharing rules to be updated
  • Cannot: Change enclave configuration directly; Approve builds or changes outside sharing rules
  • Approvals: Approves the sharing rules for each partner; their decisions follow your organization's own disclosure procedures.
  • Notified about: New requests naming partners, sharing rule drafts, and decisions approaching their review date.

ISSM

Information system security manager, cybersecurity lead. Approves the templates, each build and change, and signs off teardown evidence.

  • Sees: Templates and their baselines; Build records and baseline differences; Changes, alerts and incidents; Teardown evidence
  • Does: Approves templates for use; Reviews and approves each build before partners are added; Approves changes that affect the boundary or security settings; Signs off teardown evidence; Uses control mappings and evidence in your authorization
  • Cannot: Edit or delete audit records; Approve their own change request
  • Approvals: Approves templates, builds, security-relevant changes and teardowns; their own requests need a second designated approver.
  • Notified about: Builds awaiting review, baseline differences, escalated alerts and teardown evidence ready for sign-off.

Partner administrator

Partner liaison officer, partner network administrator. Manages their own organization's users in an enclave, within what has been approved.

  • Sees: Their organization's users and accounts in the enclave; Access reviews for their users
  • Does: Requests accounts for named users; Requests removal of users who leave; Completes access reviews for their organization
  • Cannot: See other partners' users; Change sharing rules or enclave configuration; Create accounts without approval
  • Approvals: Their account requests are approved by the mission owner.
  • Notified about: Accounts created or removed, access reviews due and end of mission.

Moraph service manager

Moraph service delivery manager. Runs the managed service: requests, builds, vendor relationships and monthly service reviews.

  • Sees: The enclave inventory, requests and change records; Alerts and incidents; Vendor cases and license usage; Teardown status
  • Does: Schedules builds once approvals are in place; Coordinates changes through your process; Manages underlying licenses and vendor cases; Runs monthly service reviews and tracks actions; Prepares evidence packages
  • Cannot: Approve disclosure, builds or changes on your behalf; See enclave content beyond what operations require
  • Approvals: Their work is governed by your approvals; nothing is self-approved.
  • Notified about: Approvals completed or returned, escalated alerts, vendor notices and overdue actions.

Moraph enclave engineer

Moraph infrastructure engineer, network security engineer. Builds, operates and tears down enclaves from approved templates, within the approvals your organization gives.

  • Sees: Enclave infrastructure and configuration; Health and access logs needed for operations; Runbooks and change requests assigned to them
  • Does: Builds enclaves from approved templates; Creates and removes accounts as approved; Applies approved changes and patches; Triages alerts and escalates confirmed issues; Carries out teardown steps and records the evidence
  • Cannot: Change sharing rules without a recorded disclosure decision; Apply an unapproved change; Sign off their own teardown
  • Approvals: Every build, change and teardown they carry out has a recorded approval from your organization.
  • Notified about: Builds and changes scheduled, alerts assigned to them and teardowns due.

Assessor or inspector (read-only)

Security control assessor, inspector general staff, internal auditor. Reviews access, disclosure, change and teardown records without changing anything.

  • Sees: Enclave inventory and templates; Disclosure references, access reviews and data movement records; Change records and teardown evidence
  • Does: Reads records within the scope granted; Exports evidence, with each export logged; Records review notes where enabled
  • Cannot: Change, approve or delete anything
  • Approvals: Their access is approved by the ISSM with a scope and an end date.
  • Notified about: Nothing by default; access granted and expiring is confirmed to the ISSM.

Permissions at a glance

ActionMission ownerFDOISSMPartner adminMoraph SMMoraph engAssessor
Request an enclaveOwn work–––Full––
Record a disclosure decision–FullView–––View
Approve sharing rules–ApprovesView––––
Approve a template or build––Approves––––
Build an enclave from a template–––––Full–
Request partner accountsOwn work––Own work–––
Create or remove accountsApproves––––Full–
Apply changes and patches––Approves––Full–
View data movement recordsOwn workFullFull–ViewViewView
Confirm end of missionOwn work–View–View––
Sign off teardown evidence––Approves–View–View
View audit trail–ViewView–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

  • Disclosure, security and operation are kept apart: the foreign disclosure officer decides what is shared, the ISSM approves builds and teardowns, and Moraph engineers carry out only what has been approved.
  • Roles are scoped to a mission, so a mission owner or partner administrator sees only their own enclave, and partners never see each other's users.
  • Partner accounts carry the mission's end date and are reviewed during the mission; nothing outlives the enclave without a recorded approval.
  • Moraph's administrative accounts are named and role-based.

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.