---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Customize team approval settings

# Customize team approval settings {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Customize how team approvals work when non-admin users create or add a team in Service Reliability Management (SRM). This feature, also known as team governance, helps you control access and align with internal policies.

## Before you begin

Role required: srm_admin or admin

## About this task

By default, team governance is active in SRM. When non-admin users request a team, SRM creates two records: a parent request and a requested item. The approval team is notified, and any member can approve the request from My approvals. Once approved, the team
is created or added, the parent request is set to `Approved`, and the requested item is set to `Closed Complete`.  
You can customize team governance by turning off approvals or changing the approval team.  
Note:  
Non-admin users are SRM managers and SRM responders. When team governance is active, admins and SRM admins can still create and add teams without approval.

## Procedure

1. Navigate to AllService Operations Workspace Admin CenterConfigurations.
2. Under Service Reliability Management, select Governance and autonomy and then select Team governance.
3. Review or update the approval options.

   | Option | Description |
   | Approval required when creating a new team | Clear this option to let non-admin users create teams in SRM without approval. |
   | Approval required when associating an existing team | Clear this option to let non-admin users add existing teams to SRM without approval. |
   |-|-|

   {#sr-add-approval-teams__choicetable_fwm_2vm_nfc}
4. Review or update the approval team for one or both options.  
   By default, the approval team is set to `SRM Team approvers`. You can view its members in `sys_user_group.list`.  
   Note:  
   Any member of the approval team can approve requests, but they need the `sn_request_read` role to view request details. Without that role, they only see the approval task.
5. Select Save to update your team governance settings.
{#sr-add-approval-teams__steps_x4h_mdz_rnb}
**Previous topic:** [Customize service approval settings](https://servicenow-prod.fluidtopics.net/npxXw18MwH0NBtW9BnIRgQ "Add an approval process to your services for governance.")  
**Next topic:** [Configure error budget actions for breached SRM SLOs](https://servicenow-prod.fluidtopics.net/NjqfMRJBWe7aJg0LAgb7PA "Configure the actions that the team can select when the error budget of a service level objective (SLO) is breached.")

*[\>]: and then