> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/approver-groups.md).

# Approver Groups

Approver group members can review and approve or decline access or credential requests. Additionally, approvers can manage other approvers within their groups. Some examples of the approver groups include: Server Room Approvers, Lab Approvers etc. 

## Approver Group Privileges

* Approval and Rejection: Every member can approve and reject relevant requests.
* Manage Members: Members can add or remove other members of their Approver Group.

#### Difference  between Approver and System Administration user groups

Approver Groups are managed and created in the same **Groups** module as the [System Administration Groups](/knowledge-hub/accessnow-user-guide/system-administration/system-administration-groups.md). AccessNow user groups and Approver Groups are interchangeable, with one key difference: Approver Groups **don't need a Role**. A Role is required only if the group needs system administration privileges.     

{% hint style="info" %}
Unlike [System Administration Group](/knowledge-hub/accessnow-user-guide/system-administration/system-administration-groups.md), the Approver Group does not require a system Role. 
{% endhint %}

## Creating a new Approver Group 

To create a new Approver Group go the system **Groups** module:

{% stepper %}
{% step %}

### Use the +Create Group button

Enter the group name and description. 
{% endstep %}

{% step %}

### Select Group members

Select Group members in the Membership section.

<figure><img src="https://3605010251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOxYzVrszbXcNBUauC0e%2Fuploads%2FJ9mE4LtTXz2nzc86AKCd%2FScreenshot%202025-07-28%20at%2012.51.53%20%E2%80%93%20ScreenClip.png?alt=media&amp;token=635e5cfe-5d50-4da3-9730-7dc9536b0d82" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Group Email is optional

You can use the Group Email field to control who receives system notifications about the requests requiring review.

* **With Group Email:** All approval emails go to the specified group email address, not to individual members.
* **Without Group Email:** Approval emails are sent to each member of the group and the emails assigned to them in the system.
  {% endstep %}

{% step %}

### Role field is optional&#x20;

The approver groups don't need any roles assigned. All aprover groups will have the approver privileges even with any role assigned.&#x20;
{% endstep %}

{% step %}

### Save the group

{% endstep %}
{% endstepper %}

## Group Management&#x20;

To manage the groups go to the **Groups** module:&#x20;

To **edit** a group, click on the group **record**, it opens the group in an edit mode.

To **delete** a group use the **Bin** button.

<figure><img src="https://3605010251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOxYzVrszbXcNBUauC0e%2Fuploads%2F4ZPzfZwOeC4LylEC2Ky4%2FScreenshot%202025-08-06%20at%2013.33.21.png?alt=media&amp;token=4cc80fb4-5e42-40d0-90e9-bda78cf91142" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/approver-groups.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.