> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/ams/help-and-support/application-help-pages/access-manager-agent/access-manager-agent-groups-page.md).

# Access Manager Agent - Groups page

The `groups` page provides the ability to create and manage AMS groups. AMS groups are stored in the Access Manager database, and can contain devices that are registered with AMS. Groups can then be used in authorization rules, and for the application of password policies.

![](https://3858442128-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fq1NRJ1mSUxsI5xgqtLGt%2Fuploads%2Fgit-blob-e77b02191302b304f9cb36d76c7bc6283947520a%2Fui-page-access-manager-agent-groups.png?alt=media)

The following groups are built-in, and their membership is automatically manged by the system;

| Group name                      | Description                                                                                          |
| ------------------------------- | ---------------------------------------------------------------------------------------------------- |
| All devices                     | All devices registered with this AMS server                                                          |
| AMS devices                     | Devices registered using a registration key                                                          |
| Microsoft Entra devices         | Devices registered using Azure authentication                                                        |
| All Windows devices             | All devices running a Windows operating system                                                       |
| All Linux devices               | All devices running a Linux operating system                                                         |
| All macOS devices               | All devices running a macOS operating system                                                         |
| AMS Windows devices             | Devices running a Windows operating system that were registered using a registration key             |
| AMS Linux devices               | Devices running a Linux operating system that were registered using a registration key               |
| AMS macOS devices               | Devices running a macOS operating system that were registered using a registration key               |
| Microsoft Entra Windows devices | Devices running a Windows operating system that were registered using Microsoft Entra authentication |

Note, built in groups cannot be edited or deleted.

### Adding a group

You can use the `Add` button to add a new custom group. You must give the group a unique name, and then use the group membership selector to add devices to the group.

## Deleting a group

Deleting a group removes it permanently from the directory. You must ensure that you unassign the group from any registration keys and password policies before you delete it.


---

# 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://docs.lithnet.io/ams/help-and-support/application-help-pages/access-manager-agent/access-manager-agent-groups-page.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.