Administration
Roles and permissions in Satellite/Geospatial Data Lake
Each role in Satellite/Geospatial Data Lake: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Satellite/Geospatial Data Lake 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 Satellite/Geospatial Data Lake. 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 data owner
Program manager, mission data steward, collection manager. Owns the holdings in the lake and makes the decisions about sources, access and retention.
- Sees: Holdings, sources and catalog statistics for their programs; Access grants and pending requests for their collections; Capacity use and forecasts for their programs; Monthly service reports
- Does: Approves new data sources and changes to existing ones; Approves or declines requests for access to their collections; Sets retention and tiering rules for their holdings; Agrees capacity plans and priorities with the program office; Reviews the monthly service report with Moraph
- Cannot: Change platform configuration directly; Grant access outside the handling rules their organization sets; Delete audit records
- Approvals: Approves sources, access to their collections and retention rules; their own access changes are applied by the ISSM.
- Notified about: Access requests for their collections, failed deliveries from their sources, and capacity nearing agreed limits.
Data engineer
Data engineer, geospatial data manager, pipeline developer. Keeps imagery flowing from approved sources into the lake in a usable, cataloged form.
- Sees: Ingest pipelines, their runs and their failures; Catalog rules and metadata quality results; Storage tiers and retention rules for their programs
- Does: Defines the format and metadata expected from each source; Investigates failed or incomplete deliveries and arranges reprocessing; Maintains catalog rules and metadata mappings; Proposes tiering and retention rules for the data owner to approve; Runs processing jobs to prepare data for analysts
- Cannot: Register a new source without data owner approval; Grant other users access to holdings; Change platform security configuration
- Approvals: New sources and retention changes they propose go to the data owner; pipeline changes that affect the platform are raised as change requests.
- Notified about: Failed ingest runs, metadata quality failures and decisions on their proposals.
Analyst
Imagery analyst, geospatial analyst, all-source analyst. Uses the holdings and analytic outputs to answer mission questions, and is the person who decides whether a candidate detection is real.
- Sees: Catalog search results for holdings they are authorized to see; Imagery and derived products within their grants; Candidate detections queued for their area or program; Lineage of any derived product they open
- Does: Searches by area, time and sensor and retrieves imagery; Submits processing jobs within the program's quota; Confirms, rejects or refers candidate detections with a recorded reason; Exports confirmed items to their reporting or exploitation tools; Requests access to additional collections
- Cannot: See holdings outside their grants; Change models, pipelines or retention rules; Delete imagery or derived products
- Approvals: Access to additional collections is approved by the data owner and applied by the ISSM.
- Notified about: New candidates in their review queue, completed jobs and decisions on access requests.
ISSM
Information system security manager, ISSO, security control assessor liaison. Answers for the security of the environment and controls what changes are made to it.
- Sees: The configuration baseline and any drift from it; Change requests, patches and their status; Access grants, privileged accounts and audit logs; Control mappings and evidence for the RMF package
- Does: Approves or rejects configuration changes and patch schedules; Applies access grants approved by data owners; Reviews audit logs and security alerts escalated by Moraph; Runs periodic access reviews; Prepares continuous monitoring submissions with the evidence Moraph supplies
- Cannot: Approve a change they raised themselves without a second approver; Edit or delete audit records; Grant access to a collection without the data owner's approval
- Approvals: Approves changes, patch schedules and security exceptions; access grants require data owner approval first.
- Notified about: Change requests awaiting approval, security alerts, configuration drift and access reviews coming due.
Moraph platform engineer
Moraph storage, compute and pipeline engineers. Keeps the environment running: storage, compute, networking inside the boundary, pipelines and monitoring.
- Sees: Platform health, capacity and performance; Pipeline runs and errors, without opening the imagery itself; Platform logs and alerts; Approved change requests and maintenance windows
- Does: Monitors the platform and triages alerts; Applies approved changes and patches in agreed windows; Expands storage and compute under approved capacity plans; Handles incidents under the agreed runbooks and reports them; Restores service and data from backups when required
- Cannot: Open or search mission imagery or analytic outputs; Grant access to holdings; Make a change that has not been approved, except emergency actions recorded and reviewed under the incident process
- Approvals: Every planned change is approved by the ISSM; emergency actions are reported to the ISSM and reviewed afterwards.
- Notified about: Platform alerts, capacity thresholds, approved changes scheduled and incidents.
Moraph service manager
Moraph service delivery manager. Is the single point of accountability for the service, and runs the monthly service review.
- Sees: Service performance, incidents and open problems; Change and patch calendars; Capacity use and forecasts; Open requests from your organization
- Does: Runs the monthly service review and agrees actions; Coordinates change requests between your teams and Moraph engineers; Tracks capacity plans and raises expansion needs early; Manages escalations to infrastructure providers
- Cannot: Open mission content; Approve changes on your organization's behalf; Grant access to holdings
- Approvals: Nothing they do changes the environment without ISSM approval.
- Notified about: Major incidents, escalations, overdue changes and capacity forecasts that need a decision.
Auditor (read-only)
Inspector general staff, security control assessor, internal auditor. Reviews how the environment is configured and who has accessed what, without being able to change anything.
- Sees: Access grants and access review results; Configuration baseline, changes and patch history; Audit logs within the scope granted; Control evidence and service reports
- Does: Searches and reads records within their scope; Exports records and reports, with each export logged; Records review notes where enabled
- Cannot: Change, approve or delete anything; See mission content unless separately granted
- 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
| Action | Data owner | Data engineer | Analyst | ISSM | Moraph eng. | Service mgr | Auditor |
|---|---|---|---|---|---|---|---|
| Register a new data source | Approves | Own work | – | View | Full | View | – |
| Run and monitor ingest pipelines | View | Own work | – | – | Full | View | – |
| Search and retrieve imagery | Full | Own work | Own work | – | – | – | – |
| Run processing and model jobs | View | Own work | Own work | – | – | – | – |
| Confirm or reject candidate detections | View | – | Own work | – | – | – | View |
| Set retention and tiering rules | Approves | Own work | – | View | Full | View | View |
| Grant access to collections | Approves | – | – | Full | – | – | View |
| Change platform configuration | – | – | – | Approves | Own work | View | View |
| Apply patches and updates | – | – | – | Approves | Full | View | View |
| Triage platform alerts | – | – | – | View | Full | View | – |
| View audit logs | View | – | – | Full | 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 run the platform but do not open mission imagery or analytic outputs; their access is limited to the infrastructure and is recorded like everyone else's.
- Nobody approves their own change: changes raised by Moraph or your staff are approved by the ISSM, and changes the ISSM raises need a second approver.
- Roles are configured with you during design. Access can be limited by program, collection and handling marking, and follows the groups in your identity provider.
- Work in classified environments happens under your organization's authority.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.