Administration
Roles and permissions in "Civic-Secure" Microsoft 365
Each role in "Civic-Secure" Microsoft 365: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to "Civic-Secure" Microsoft 365 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 "Civic-Secure" Microsoft 365. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in GCC as part of the managed service.
Roles
Agency user
Patrol officer, detective, court clerk, dispatcher, probation officer. Uses email, Teams, SharePoint and OneDrive for daily work, including handling criminal justice information under the agency's rules.
- Sees: Their own mailbox, files and the Teams and sites they belong to; Labels and policy tips that tell them when content is restricted; Content shared with them by colleagues and approved partners
- Does: Signs in with multi-factor authentication from a compliant device; Labels documents and email that contain criminal justice information; Shares content with colleagues and approved partner agencies; Reports suspicious email and lost devices
- Cannot: Share labeled content with recipients the policy does not allow; Sign in from unmanaged devices where conditional access blocks it; Remove a label applied by policy without justification
- Approvals: Overriding a data loss prevention warning, where the policy allows it, requires a business justification that is logged.
- Notified about: Policy tips when content is restricted, sign-in prompts, and messages from the agency about security.
Local Agency Security Officer
LASO, CJIS coordinator, terminal agency coordinator. Is responsible for the agency's CJIS compliance and is the agency's contact with the state CJIS Systems Agency.
- Sees: The configuration baseline and how each requirement is met; Security alerts and how they were handled; Access reviews, administrator lists and audit logs; Monthly service review reports
- Does: Approves changes that affect security-relevant settings; Certifies access reviews; Decides on alerts involving a possible release of criminal justice information; Coordinates audits with the state CJIS Systems Agency; Confirms personnel screening is complete before access is granted
- Cannot: Edit or delete audit logs; Apply configuration changes directly unless also given an admin role; Waive requirements set by the CJIS Security Policy
- Approvals: Approves security-relevant configuration changes, privileged access and closure of security findings.
- Notified about: Security alerts needing an agency decision, changes awaiting approval, access reviews due and audit dates.
Agency IT administrator
City or county IT staff, agency systems administrator. Supports users and devices day to day within the limits the baseline sets.
- Sees: Users, groups and licences; Device inventory and compliance status; Service health and support tickets with Moraph
- Does: Creates and disables user accounts; Enrolls and retires devices in Intune; Resets authentication methods after identity is confirmed; Raises change requests and support tickets with Moraph
- Cannot: Change conditional access, labeling or data loss prevention policies without approval; Grant global administrator rights; Turn off audit logging
- Approvals: Changes to security policies go through the change process and LASO approval.
- Notified about: Non-compliant devices, accounts not used for the period policy sets, and updates on their tickets.
Records and legal staff
Records manager, public records officer, city attorney's office staff. Manages retention, legal holds and searches for litigation and public records requests.
- Sees: Retention policies and labels; eDiscovery cases and holds they are assigned; Search results within the scope of each case
- Does: Requests retention policy changes in line with the records schedule; Places and releases legal holds; Runs searches and exports results for review; Records the basis for each search
- Cannot: Change security policies; Search outside the cases they are assigned; Delete content under hold
- Approvals: eDiscovery case access is approved by the agency's designated legal or records lead.
- Notified about: Holds placed or released, and searches completed.
Moraph M365 engineer
Moraph Microsoft 365 administrator, security operations analyst, service manager. Configures and monitors the tenant for the agency, keeps it aligned with the baseline and supports the agency's audit.
- Sees: Tenant configuration, service health and security alerts; Configuration drift and Microsoft service change notices; Audit logs needed to investigate an alert, as the agency authorizes
- Does: Applies approved configuration changes; Triages security alerts and escalates decisions to the agency; Corrects configuration drift or raises it for approval; Raises support cases with Microsoft; Prepares the monthly service review and audit evidence
- Cannot: Access mailbox or file content without explicit agency authorization; Apply changes to security-relevant settings without LASO approval; Release or disclose criminal justice information
- Approvals: Changes are approved by the agency; Moraph's administrative access is approved by the LASO.
- Notified about: Security alerts, drift detected, Microsoft service changes and approved changes ready to apply.
Auditor (read-only)
State CJIS Systems Agency auditor, internal auditor, city auditor. Reviews how the tenant meets requirements, without changing anything.
- Sees: The configuration baseline and requirement mapping; Audit log extracts and access review results; Security findings and how they were closed
- Does: Reviews evidence provided for the audit; Requests additional evidence through the LASO; Records findings for the agency
- Cannot: Change any configuration or access; See mailbox or file content unless the agency grants it for a specific review; Keep access after the audit ends
- Approvals: Any direct access is approved by the LASO with a scope and end date.
- Notified about: Nothing by default; evidence is provided through the LASO.
Permissions at a glance
| Action | User | LASO | Agency IT | Records/legal | Moraph eng. | Auditor |
|---|---|---|---|---|---|---|
| Use email, Teams and files | Own work | Own work | Own work | Own work | – | – |
| Apply sensitivity labels | Own work | Own work | Own work | Own work | – | – |
| Create and disable user accounts | – | View | Full | – | Full | – |
| Enroll and retire devices | – | View | Full | – | Full | – |
| Change conditional access and DLP policies | – | Approves | – | – | Full | – |
| Change retention policies | – | Approves | – | Own work | Full | – |
| Place legal holds and run eDiscovery | – | – | – | Full | – | – |
| Triage security alerts | – | Approves | View | – | Full | – |
| Grant administrator roles | – | Approves | – | – | Full | – |
| View audit logs | – | View | View | View | View | View |
| Certify access reviews | – | Approves | View | – | 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
- Security-relevant changes are proposed by Moraph or agency IT and approved by the Local Agency Security Officer before they are applied, and the record of each approval is kept.
- Moraph engineers manage configuration, not content. They do not open mailboxes or files without explicit authorization from the agency, and they never release criminal justice information.
- Roles are mapped to groups in Microsoft Entra ID and reviewed periodically. Auditors receive evidence through the LASO, or temporary read-only access with a scope and end date.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.