Administration
Roles and permissions in ServiceNow for Federal Service Management
Each role in ServiceNow for Federal Service Management: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to ServiceNow for Federal Service Management 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 ServiceNow for Federal Service Management. 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
Requester
Federal employee, contractor, detailee. Gets help or asks for something through one portal and can see where their request stands.
- Sees: The service catalog and knowledge articles available to them; Their own incidents and requests with status and comments; Approvals waiting on them if they are a supervisor or sponsor
- Does: Signs in with their PIV card through the agency's identity provider; Reports problems and submits catalog requests; Adds comments and attachments to their own tickets; Approves requests for their staff when named as approver; Rates resolved tickets where the agency enables surveys
- Cannot: See other people's tickets unless the agency grants it; Change the priority or assignment of a ticket; Approve their own request
- Approvals: Catalog items the agency marks for approval go to the requester's supervisor or sponsor before work starts.
- Notified about: Ticket received, status changes, requests for more information, and resolution.
Service desk agent
Help desk technician, tier 1 or tier 2 support specialist. Works the incident and request queue, resolves what it can at first contact, and routes the rest to the right group.
- Sees: Incidents and requests in their assignment groups; Requester details and recent ticket history; Knowledge articles and known issues; Their own open work by priority and age
- Does: Logs tickets taken by phone or walk-up; Resolves incidents and records the resolution; Reassigns tickets to fulfillment groups; Proposes knowledge articles for approval; Escalates tickets in line with the agency's priority rules
- Cannot: Complete credentialing tasks reserved for the credentialing office; Change catalog items, workflows or assignment rules; Grant roles or group membership
- Approvals: Their work needs no approval; knowledge articles they draft are approved by a knowledge owner before publication.
- Notified about: Tickets assigned to them or their group, tickets nearing the response targets the agency set, and requester replies.
Fulfillment group member
Credentialing specialist, PIV issuer, desktop support technician, network operations staff. Completes the tasks routed to their group, such as resetting a PIV PIN in person or preparing a token for issuance by the agency's issuing office.
- Sees: Tasks assigned to their group with the request details needed; The request's approval status and earlier tasks; Their group's queue by age
- Does: Accepts and completes assigned tasks; Records identity checks and actions in the task notes; Returns tasks to the requester or agent for missing information; Closes tasks with an outcome
- Cannot: See tasks for other fulfillment groups unless granted; Skip a required approval step; Change the workflow for their catalog items
- Approvals: Tasks only reach them after the approvals the catalog item requires have been given.
- Notified about: New tasks for their group, and tasks waiting longer than the agency's target.
Agency service owner
Service desk manager, IT service management lead, bureau IT lead. Owns the service for the agency: sets priorities and policy, approves changes and decides who has access.
- Sees: All tickets and dashboards across their bureaus; Change requests, their estimates and test results; Monthly service review reports and open risks; Access lists for agents, fulfillment groups and administrators
- Does: Approves or rejects change requests; Sets catalog approval rules and assignment policy; Certifies access in periodic access reviews; Approves knowledge and communications to employees; Reviews service performance with Moraph each month
- Cannot: Edit or delete platform audit logs; Release a change to production that has not passed testing; Bypass ServiceNow's terms or licence limits
- Approvals: Approves changes, new catalog items, privileged access and release schedules.
- Notified about: Change requests awaiting decision, major incidents, access reviews due, and the monthly service review.
Moraph service engineer
Moraph ServiceNow administrator, platform engineer, service manager. Runs the instance for the agency: monitors health and integrations, makes approved configuration changes and keeps the baseline and control documentation current.
- Sees: Platform health, integration status and system logs; Configuration, update sets and the agreed baseline; Ticket data only where needed to fix a reported problem
- Does: Builds and tests approved changes in non-production; Releases approved changes on the agreed schedule; Triages platform alerts and raises cases with ServiceNow; Plans and regression tests ServiceNow release upgrades; Prepares the monthly service review and control evidence
- Cannot: Release a change the agency has not approved; Grant access to agency users without agency approval; Approve requests or complete fulfillment tasks on the agency's behalf
- Approvals: Every production change is approved by the agency service owner; emergency fixes are reported to the agency and recorded.
- Notified about: Platform and integration alerts, approved changes ready for release, and ServiceNow notices about releases and incidents.
Auditor or assessor (read-only)
ISSO, security control assessor, inspector general staff, internal auditor. Reviews tickets, configuration evidence and logs for assessments and audits, without changing anything.
- Sees: Tickets and approvals within the scope granted; Configuration baseline, change history and control documentation; Audit logs and access review results
- Does: Searches and reads records within their scope; Exports evidence, with each export logged; Records assessment notes outside the operational queues
- Cannot: Create, change or close tickets; Change configuration or access
- Approvals: Access is approved by the agency service owner with a scope and an end date.
- Notified about: Nothing by default; access granted and expiring is confirmed to the approver.
Agency administrator
Agency platform administrator, identity and access team member. Manages agency users, groups and role assignments, within limits the service owner sets.
- Sees: Users, groups and role assignments; Identity provider group mappings; The record of access changes
- Does: Adds and removes users or maps them from identity provider groups; Assigns users to assignment and fulfillment groups; Runs access review reports; Disables accounts for departing staff
- Cannot: Grant privileged administrator roles without service owner approval; Change workflows or catalog items; Edit audit logs
- Approvals: Privileged role grants are approved by the agency service owner.
- Notified about: Access reviews due and accounts not used for the period agency policy sets.
Permissions at a glance
| Action | Requester | Agent | Fulfiller | Service owner | Moraph eng. | Auditor | Agency admin |
|---|---|---|---|---|---|---|---|
| Submit requests and incidents | Own work | Full | Full | Full | – | – | – |
| Work and resolve incidents | – | Full | Own work | Full | – | – | – |
| Approve catalog requests | Own work | – | – | Approves | – | – | – |
| Complete fulfillment tasks | – | – | Own work | View | – | – | – |
| Publish knowledge articles | – | Own work | – | Approves | – | – | – |
| Request a configuration change | – | – | – | Full | – | – | – |
| Approve a configuration change | – | – | – | Approves | – | – | – |
| Build and release approved changes | – | – | – | View | Full | – | – |
| Manage users and groups | – | – | – | Approves | View | – | Full |
| Grant privileged roles | – | – | – | Approves | – | – | Own work |
| View audit logs and change history | – | – | – | View | 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
- Nobody approves their own request or their own change: requests go to a supervisor or sponsor, and every production change is approved by the agency service owner before Moraph releases it.
- Roles, assignment groups and fulfillment groups are configured with you during implementation and can be limited by bureau, component or location.
- Moraph engineers work on the platform under the agency's approval and do not complete fulfillment tasks or approve requests.
- Users sign in with their PIV card through the agency's identity provider, and group membership can follow its groups. Auditors and assessors get temporary read-only access with a defined 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.