---
title: Tag Groups
id: "en:tpm:ROOT:tag_groups.adoc"
site: en
component: tpm
module: ROOT
version: 3.0
lang: en
url: "https://help.rtlscloud.io/en/tpm/3.0/tag_groups.html"
source_repo: "https://github.com/iot-invent/rtlscloud-tpm.git@3.0.x"
source_path: docs/en/modules/ROOT/pages/tag_groups.adoc
---

# Tag Groups

Groups bundle tags. They are not merely an organizational aid but the unit by which access is authorized: a third-party system receives exactly the events of the tags in the groups assigned to it.

## Reference

![Tag Groups](_images/tpm_app_tag_groups.png)

| Module | Description |
| --- | --- |
| ![refresh](_images/refresh.svg) Refresh | Reloads the list |
| ![plus](_images/plus.svg) New | Creates a group |
| ![edit](_images/edit.svg) Edit | Opens the selected group for editing |
| ![delete](_images/delete.svg) Delete | Removes the group |
| ![info](_images/info.svg) Info | Number of groups shown |

## Attributes

| Field | Type | Description |
| --- | --- | --- |
| Name | Text | Display name of the group |
| Notes | Text | Free text, usually what the group is for |

## Usage

Three rules that together explain why events arrive or do not:

-   A tag belongs to **at most one** group.

-   A credential can be granted **several** groups, and several credentials can be granted the same group.

-   A tag **without** a group produces events that no credential collects. They are processed and recorded but have no recipient.

The last rule is the most common reason for a third-party system being connected and still receiving nothing. The second most common is a credential without an assigned group — see [Clients](clients.md).

## Deleting a Group

Deleting a group does not remove the tags in it. They are left without a group afterwards — and their events no longer reach any target system until you assign them to another group. Before deleting, check in [Tags](tags.md) which tags are affected.