> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/command-centre/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/command-centre/accessnow-user-guide/system-administration/system-administration-groups.md). # System Administration Groups ## User Groups User groups are used in the system to enable privilege and approver management. There are two main types of groups: Approver Groups and System Management Groups. ## Approver Groups Approver Groups approve access or credentials. These groups do not require a role. Additionally, approvers can add other approvers to their groups. They are described in more detail here: [Approver Groups](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/approver-groups.md). ## System Administration Groups These groups are essential for managing and configuring the AccessNow system. They require an assigned **Role** to grant them the necessary system privileges. They can also serve as Approver Groups. {% hint style="info" %} System Administration Groups can also serve as Approver Groups in workflows. {% endhint %} Examples of System Administration Groups include: * **System Administrators**: Responsible for overarching system management and configuration tasks. * **Installers**: Handle installation and setup processes within the system. Assigning roles to these groups ensures smooth administration and operation of the system. A system management group consists of: * **Role** - Assigning a role is essential for the system administration group as it determines the privileges users in that group have. Role names are usually very similar as the names of the groups. Some examples include: "System Administrators," "Site Manager," "Workflow Managers," etc. * **Users** – By adding users to a system administration group, they receive the privileges assigned through the assigned Role. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.security.gallagher.com/command-centre/accessnow-user-guide/system-administration/system-administration-groups.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.