> ## Documentation Index > Fetch the complete documentation index at: https://docs.plerion.com/llms.txt > Use this file to discover all available pages before exploring further. # Integration groups > Group integrations by their AWS Organizations account tags or by tags you define in Plerion, and filter by group With **[Integration groups](https://app.plerion.com/settings/integration-groups)**, you can group integrations that share a tag, and filter by group instead of selecting accounts one by one. Tags come from your AWS accounts, or from tags you define on an integration in Plerion. *** ## How integration groups work An integration group is a set of integrations that share a tag. Select a tag key, and each of its values becomes a group. For example, the key `Division` collects integrations tagged `Division=payments` into the group **Division:payments**. Group membership is derived from each integration's tags: its AWS account tags, and any [tags defined in Plerion](#define-tags-on-an-integration), which replace the AWS account tag with the same key. * Plerion reads account tags when your management account or delegated administrator integration is scanned, and updates group membership automatically. * Saving tags defined in Plerion updates the groups that use those keys within a few seconds. * Newly onboarded integrations join their groups shortly after registration. * Plerion recalculates every group at least once a day. * Matching is case-sensitive: `BusinessUnit:dev` and `BusinessUnit:Dev` are different groups. Groups are built from the tags on AWS **accounts** in AWS Organizations and from [tags defined in Plerion](#define-tags-on-an-integration), not from tags on resources. *** ## Prerequisites * An integration that can read your AWS organization: your management account, or a member account granted read access by a delegation policy. See [Delegate AWS Organizations read access to a member account](/guides/integrations/aws/additional-aws-configurations/organizations-delegated-administrator). If you cannot tag your AWS accounts, [define tags in Plerion](#define-tags-on-an-integration) instead. * The **Organization Admin** role, to configure integration groups. *** ## Steps to select tag keys The page lists the tag keys collected from your AWS accounts and the groups your current selection produces. Integration groups settings page with the tag keys card and the groups table The **Tag keys** card lists every tag key found on your integrations, from AWS accounts and from tags defined in Plerion, with the values found for each key. Check each key you want to group by, and each of its values becomes a group. You can select up to 20 keys. If a key or value you expect is missing, make sure the tagged account has been onboarded on the **Integrations** page. Tag keys card showing discovered keys with their tag values While you have unsaved edits, the page shows an **Unsaved changes** chip, and **Discard changes** returns to the saved selection. On save, Plerion confirms with **Tag keys saved. Groups are updating now.** The groups table refreshes within a few seconds as the recalculation completes. The groups table shows each group's tag key and value, the integrations it contains, and when it was last computed. Integration names link to their settings pages. *** ## Define tags on an integration Tag your AWS accounts in AWS Organizations where you can: Plerion reads those tags on every scan, so a newly tagged or re-tagged account moves between groups with no change in Plerion. When tagging the account is not an option, define tags on the integration in Plerion instead. Both kinds of tag feed the same groups. Go to **Settings > Integrations** and select the integration. The **Tags** section lists the tags defined in Plerion and the tags read from the cloud account. Add a tag by typing a key and a value, or pick a key already used on another integration to keep your keys consistent. Keys and values are case-sensitive: `Env` and `env` are different keys. An integration can carry up to 50 tags defined in Plerion. Groups that use one of the changed keys recalculate within a few seconds. A tag defined in Plerion replaces the AWS account tag with the same key. Remove the Plerion tag to go back to the AWS value. You can also replace an integration's Plerion tags through the API. See [Replace an integration's user-defined tags](/api-reference/integrations/replace-user-defined-tags). *** ## Removing a tag key Deselecting a key and clicking `Save` opens the **Remove tag keys?** confirmation. The groups derived from that key stop matching integrations and show as **Inactive**. Reselecting the key restores them. Remove tag keys confirmation modal listing the affected groups *** ## Filter by integration group The **Integration group** filter narrows results to the integrations currently in the group. It is available on: * **Findings**, **Assets**, **Vulnerabilities**, and **Alerts** * **Top risks**, **Compliance**, and **Data security** * Findings, alerts, and vulnerability widgets in **Custom dashboards** * Finding, asset, and vulnerability conditions in **Workflows** On the **homepage dashboard**, pick an integration group in the global filter to scope every widget to the group. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.