---
title: Tags
summary: 'A tag is a flexible label you stick on users and SIP devices to group them by attribute, role, or any other axis your tenant cares about. Tags overlap freely, unlike groups.'
section: features
tags:
  - crud
  - telephony
  - attributes
updated: '2026-08-12'
---

> A **tag** is a flexible label you stick on users and SIP devices to group them by any axis your tenant cares about. Tags overlap freely: one user can carry as many as you like, which is exactly what a [group](groups.md) cannot do.

## Overview

A tag is the "and also" dimension. Where [Groups](groups.md) carve users into mutually-exclusive teams (one group per user), tags overlap freely - a user might carry *senior*, *English-speaking*, *on-call-rotation*, and *VIP-support* at once. You decide what each tag means.

## What it does

A tag does not affect callers directly. It affects *who gets the call* when a routing entity filters by tag. Tags become routing-relevant when consumed by:

- [Pools](pools.md) - both Include and Filter phases accept tags as a criteria type.
- [Multicasts](multicasts.md) - target everyone with a given tag.
- [Call flow steps](call_flow_steps.md) - the Dial step type can target tags.

Editing a tag's membership takes effect on the next routing evaluation - there is no need to re-save the consuming pool, multicast, or step.

> [!IMPORTANT]
> Tag names are case-sensitive and must be unique on the tenant, so *Sales* and *sales* are distinct tags. Decide on a casing convention before creating tags at scale.

## See also

- [Users](users.md) - the primary tag-bearer.
- [SIP devices](sip_devices.md) - the secondary tag-bearer.
- [Pools](pools.md) - the main consumer.
- [Multicasts](multicasts.md) - paging by tag.
- [Groups](groups.md) - the mutually-exclusive alternative.

```yaml fields
name:
  label: Name
  api: name
  tab: General
  hint: 'The display name of the tag. Must be unique within your PBX. Use lowercase-with-dashes (for example, on-call or vip-support) to avoid case-sensitivity issues.'
description:
  label: Comment
  api: description
  tab: General
  hint: 'Optional note describing the purpose of this tag and when to apply it.'
users:
  label: Users
  api: users
  tab: General
  hint: 'Users assigned to this tag. Tagged users can be targeted together in call flows, pools, and other routing configurations.'
sipDevices:
  label: 'SIP devices'
  api: sipDevices
  tab: 'SIP devices'
  hint: 'SIP devices assigned to this tag. Grouping devices under a tag makes it easier to manage them in bulk and filter them in lists.'
```