> ## Documentation Index
> Fetch the complete documentation index at: https://docs.luumen.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Host groups

> Group similar hosts by shared properties so you can assign compliance checks to the right hosts and review results at the group level.

A **host group** is a saved set of hosts filtered by shared properties. Groups are the unit you assign compliance checks to: a check assigned to "Linux production database hosts" runs only against the hosts that match that filter. Groups also give you a roll-up view of compliance status — useful when you have hundreds of hosts and want to see the health of each part of your fleet at a glance.

## Why groups exist

Without groups, every check would either run against every host (noisy) or have to be assigned host-by-host (tedious). Groups give you a stable name and filter for a class of hosts:

* "AWS production"
* "Linux production database hosts"
* "Windows file servers"
* "Non-production sandbox"

When new hosts join the fleet, they fall into the matching groups automatically — no manual reassignment needed.

## Create a group

<Steps>
  <Step title="Open the Hosts page">
    Go to **Hosts → All hosts** in the Luumen UI.
  </Step>

  <Step title="Build the filter">
    Click **Filters → Add** and combine the properties you want. For example, `vendor = AWS` AND `os_family = Linux`. You can add as many conditions as you need.
  </Step>

  <Step title="Save as group">
    Once the filter shows the hosts you want, click **Save as group**. Provide a **Name** and **Description** in the modal that appears and click **Create group**.
  </Step>

  <Step title="Confirm">
    The new group appears under **Hosts → Host groups**. The count next to the group name shows how many current hosts match.
  </Step>
</Steps>

## How filters work

Filters are evaluated on every agent run, against the most recently captured properties. The group's membership is dynamic — a host whose `vendor` changes from `AWS` to `Azure` automatically leaves the AWS group on the next run.

You can filter on any property the agent collects. Common starting points:

| Property                   | Use case                                                                                                             |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| `vendor`                   | Group by cloud (AWS, Azure, GCP) or on-prem                                                                          |
| `os_family` / `os_version` | Group by Linux vs Windows, RHEL vs SLES, etc.                                                                        |
| `environment` (custom)     | Split production from non-production                                                                                 |
| Application properties     | Group by application role (e.g., web servers vs databases, or — with the SAP integration enabled — by SAP component) |
| Hardware properties        | Group by host class for performance baselines                                                                        |

If a property you want to filter on isn't on the host, it won't appear in the filter dropdown. See [What the agent collects](/enterprise/data/what-the-agent-collects) for what's available and how to extend the set.

## Edit a group

To change a group's filter or description:

1. Go to **Hosts → Host groups**.
2. Click the group, then click **Edit**.
3. Update the filter, name, or description and save.

Membership refreshes on the next agent run.

## Delete a group

Deleting a group removes its filter and unassigns its checks. The hosts themselves are unaffected — they remain in any other groups they belong to, and historical check results are preserved.

## Assigning checks to groups

Groups are the connection point between captured data and compliance enforcement. To attach a check to a group:

1. Go to **Hosts → Host groups → \[Group name]**.
2. Click **Assign check** and pick the check from the list.

Or assign at check creation time — see [Assigning checks to groups](/enterprise/compliance/assigning-checks).

## Group views in the UI

The **Acceptance to Run → Overview** page renders results grouped by host group. Each group shows a roll-up compliance percentage, error counts, and a drill-down into individual hosts and their check results. This is the view your team will use day-to-day to spot parts of the fleet that are drifting.