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

# Tags: how agents, sources and leads connect

> Tags join a lead source to the agent that works it, and they are the filter the lead lists, the Inbox and the Campaigns Report all share.

export const UiPath = ({children}) => {
  const parts = String(children).split(/\s*(?:→|>)\s*/).filter(Boolean);
  return <span className="pl-path">
      {parts.map((part, index) => <span key={`${index}-${part}`}>
          {index > 0 && <span className="pl-path__sep">→</span>}
          {part}
        </span>)}
    </span>;
};

export const Screenshot = ({id, alt, caption, frame = 'browser', url, marks = [], lang = 'en', workspace = 'northwind-outbound'}) => {
  const src = `/images/screenshots/${lang}/${id}.png`;
  const chrome = url ? `app.pipelime.ai/${workspace}${url}` : 'app.pipelime.ai';
  return <figure className={`pl-shot pl-shot--${frame} not-prose`}>
      <div className="pl-shot__frame">
        {frame !== 'bare' && <div className="pl-shot__bar">
            <span className="pl-shot__dots">
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
            </span>
            <span className="pl-shot__url">{chrome}</span>
          </div>}
        <div className="pl-shot__media">
          <img src={src} alt={alt} loading="lazy" />
          {marks.map(mark => <span key={mark.n} className="pl-shot__mark" style={{
    left: `${mark.x}%`,
    top: `${mark.y}%`
  }} aria-hidden="true">
              {mark.n}
            </span>)}
        </div>
      </div>
      {caption && <figcaption className="pl-shot__caption">{caption}</figcaption>}
    </figure>;
};

A tag is a label on a lead or a company. It is also the only thing a lead source, an import or a connected channel account shares with the agent that works whatever they find.

<div className="pl-availability">
  <div className="pl-availability__row">
    <div className="pl-availability__label">Where</div>
    <div className="pl-availability__value"><span className="pl-path">Leads<span className="pl-path__sep">→</span>Prospects</span></div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">Your role needs</div>
    <div className="pl-availability__value">Read access to Prospects <code>read-leads</code>. Admin, Member and Viewer have it by default.</div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">To create or change</div>
    <div className="pl-availability__value"><code>create-leads</code> to add one, <code>update-leads</code> to change one, on top of the permission above.</div>
  </div>

  <div className="pl-availability__note">If you cannot find this in your sidebar, your workspace may have a custom menu configuration. Contact support and we will check it for you.</div>
</div>

One control does all of it. The same picker sits in a list's filter bar, on a lead's own page and inside the dialog that connects a channel account. Closed with nothing chosen it reads **Select tags**, or **Select tag** where only one is allowed, and it reads that whatever placeholder text the screen around it sets, because the picker ignores the placeholder entirely. The Inbox is the one place that empty state is different: there the picker collapses to a bare tag icon next to the search box, with a count beside it once you have picked something.

| Where a tag comes from                                                  | What it does                                                                                                       |
| ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| A lead source, created or added to an agent                             | Tags every company it finds, and every person it finds at that company                                             |
| Saving a person from Manual Search, or importing a CSV                  | Required before you can save; the destination tag is what puts them in your pipeline                               |
| Connecting a WhatsApp, Instagram or MercadoLibre account with a tag set | Tags every lead that account's conversations create, automatically, from then on                                   |
| A web form or a website tracker                                         | Tags the company each submission, or each identified visit, creates. Optional on a web form, required on a tracker |
| Picking tags in a list or report's filter bar                           | Narrows what you're looking at to leads or companies carrying at least one of them                                 |
| The **Tags** field on a lead's or a company's own page                  | Add or remove tags on that one record by hand, any time, however it got its first one                              |

## How it behaves

### A tag is created inline, or gets created for you

The picker opens on a search box. Directly under it, above your existing tags, sits a pinned **Create new tag** action, for the roles that can create one. It opens a small dialog: type a name, pick a preset color or turn on **Use a custom color** for a hex value, watch the chip in the live preview, and choose **Create tag**. Type into the search box instead and, as long as no active tag already has that name, the list offers an inline option to create it there and then, with a random color. That option takes the name from the search box with its first letter capitalized, so typing `enterprise` creates `Enterprise`.

<Screenshot id="leads/tags--create-tag" url="/leads/prospects" alt="The Create new tag dialog open over the Prospects page's tag picker, with a name typed in, a grid of preset colors, and a live preview chip" caption="The same dialog opens from every tag picker in the product, not just this one." />

Some tags are created without you opening this dialog at all. Building an agent creates its tag as the first of three steps, tag then lead source then agent, named after the agent itself, with a number appended if that name is already taken. If the wizard adopts a source you already have instead of building a new one, the new tag is added to that source rather than a source being created. Adding a source to an agent that has no tag yet works the same way: it creates one, named after the agent, and puts it on the agent before the new source is created.

### The tag is the join, wherever a lead enters your workspace

A lead source's tag is what a company inherits the moment that source finds it, along with every person the source then finds at that company. It does not wait for you to save anything by hand. A source you add from inside an agent's own page never asks you to pick a tag for it either: the form has no tag field, because the source is created carrying the agent's own tag.

Manual Search and importing a CSV work the other way around, and both refuse to move without a tag. **Save** on a Manual Search result with no tag chosen warns you and opens the picker instead of saving. The results header carries a reminder to choose one, and that reminder stays put whether or not you already have, next to an information bar above the table that disappears the moment you do. The CSV import's own review step marks its tag field required and keeps the button that starts the import disabled until you pick one. Run either of them from inside an agent, through its **Add leads** action, and there is nothing to pick: the destination tag is the agent's, fixed, and the tag field is hidden.

Connecting a WhatsApp, Instagram or MercadoLibre account carries an optional tag field of its own. Pick a tag there and every lead that account's conversations create is tagged with it automatically, with nothing further to do. The LinkedIn connect dialog has a **Tag** field that looks the same and does something different: the tag is stored on the account itself, and it is never put on the leads that account produces.

None of this is permanent. A lead's own page, and a company's own page, each carry their own **Tags** field, and adding or removing a tag there takes effect on that record straight away, whatever put the first one on. Putting an *existing* tag on a lead needs the same permission that lets you edit anything else about that lead; on a company, the same permission that lets you edit the company. That is a different, narrower grant than the one that lets you create a new tag or archive one.

### An agent reaches only the companies wearing its tag, and a tagless agent is not the exception

This is the rule that makes a tag more load-bearing than it looks. An agent with a tag can only ever open a conversation with a company that carries at least one of the same tags. An agent with *no* tag at all is not unfiltered: it can only reach companies carrying no tags of their own, which is its own narrow segment, not a fallback for whatever else is left over. An untagged agent and a tagged company never see each other, in either direction. The same rule decides which people it can write to when there is no company involved at all, reading the tags on the lead instead.

Change which tag an agent uses from <UiPath>Outreach → AI Agents</UiPath>: open the agent, its **Settings** tab, then **Advanced**, and find the **Audience tags** field (every field on that tab is covered in full on [Agent settings reference](/en/ai-agents/agent-settings-reference)). A warning sits right under it for a reason: changing this changes which leads the agent contacts.

<Screenshot id="leads/tags--source-tag" url="/ai-agents/12?tab=settings&section=advanced" alt="The Advanced section of an agent's Settings tab, with its tag shown as a colored chip under the Audience tags field and a warning that changing tags changes which leads the agent contacts" caption="This is where an agent's own tag lives. Its Sources tab never shows it, on any row." />

If a tag change would leave one of the agent's own sources sharing no tag with it any more, saving stops and asks you first, source by source: **Also add tag to lead source** keeps it attached by adding the new tag to the ones it already has, or **Detach** lets it go. A detached source keeps running exactly as before; it just stops feeding this agent, and becomes available for a different agent to adopt instead.

### A tag is the filter every lead list shares

Open <UiPath>Leads → Prospects</UiPath> and its tag filter is the same picker, set to take more than one tag at once. Companies and the Campaigns Report carry the same control in their own filter bar, and the Inbox carries the collapsed version of it. Pick two or more tags and a list shows anything carrying at least one of them, not only the leads or companies carrying all of them.

<Screenshot id="leads/tags--tag-filter" url="/leads/prospects" alt="The tag filter open on the Prospects page, several tags listed and one already checked" caption="Picking a tag here doesn't close the menu, so you can check as many as you want before moving on." />

On the Prospects and Companies lists, each row also carries its own **Tags** column. It shows the first tag as a small colored chip, and, when the row has more than one, a "+2 more" counter next to it that lists the rest in a tooltip. Prospects draws that counter as a second chip and Companies as a line of text, but they say the same thing.

### Creating and archiving a tag are gated separately from selecting one

Anyone who can open a tag picker at all can select from your existing tags for whatever they are editing. Creating a tag and archiving one are two separate permissions on top of that: `create-tags` puts **Create new tag** and the inline create option in the list, and `update-tags` puts the **Archive tag** button on a tag's row, which appears when you hover it. Admin and Member have both by default. Viewer has neither, and cannot edit a lead or a company either, so a Viewer sees every tag in every picker, can filter a list with them, and cannot change a tag or put one on a record.

### Archiving hides a tag rather than deleting it

Archiving sets a tag inactive. From then on it is tucked behind a **Show archived tags** toggle at the bottom of the picker, which appears once you have archived at least one, and it is still selectable from inside that expanded section. Archiving does not touch whatever already carries the tag: a lead, a company, a lead source or an agent that had it keeps it, and a list still prints its name in the Tags column. The picker is the one place that gets it wrong, because it looks names up only among active tags, so a record carrying a tag you have archived shows an unnamed chip in its **Tags** field.

There is no delete action for a tag anywhere in the interface, and no way to rename one either. **Archive tag** and its opposite, **Restore tag**, are the only things you can do to a tag once it exists.

## Limits

|                                                            |                                                                                                                                                |
| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Can a tag be renamed                                       | No. Create, archive and restore are the only tag-level actions in the interface                                                                |
| Can a tag be deleted                                       | No delete control anywhere in the interface                                                                                                    |
| What archiving does                                        | Sets it inactive: out of the picker's main list, still selectable behind **Show archived tags**, and untouched on anything already carrying it |
| Who can create a tag                                       | A role with `create-tags`. Admin and Member have it by default; Viewer does not                                                                |
| Who can archive or restore a tag                           | A role with `update-tags`, which is separate from `create-tags`. Admin and Member have it by default; Viewer does not                          |
| Who can put an existing tag on a lead or a company         | Whoever can edit that record, which is not a tags-specific permission                                                                          |
| How many tags one lead, company, source or agent can carry | The picker sets no limit                                                                                                                       |
| How long a tag name can be                                 | Capped. The create dialog counts your characters and stops accepting them at the cap                                                           |
| What an agent with tags reaches                            | Only companies (or, with no company involved, leads) carrying at least one of the same tags                                                    |
| What an agent with no tags reaches                         | Only companies (or, with no company involved, leads) carrying no tags at all: its own narrowest segment, never "everything"                    |
| Where to change an agent's tags                            | Its own page: the **Settings** tab, under **Advanced**, in **Audience tags**                                                                   |
| A tag change that would orphan a source                    | Asked about before it saves, per source: keep it (add the new tag too) or let it detach                                                        |

## Related

<CardGroup cols={2}>
  <Card title="Lead sources: add, edit limits, pause" icon="route" href="/en/ai-agents/lead-sources">
    Why adding a source can create a tag on the spot, and what an orphaned source actually is.
  </Card>

  <Card title="Manual Search (the lead picker)" icon="search" href="/en/finding-leads/manual-search">
    The other tag picker that refuses to let you save without a choice, and why.
  </Card>

  <Card title="Working the Prospects list" icon="table" href="/en/leads/prospects-list">
    Every column and filter on the list where a tag most often gets used, including the Tags column itself.
  </Card>

  <Card title="Campaigns Report" icon="chart-line" href="/en/analytics/campaigns-report">
    The report's own filter bar takes a campaign, tags, or both before it runs.
  </Card>
</CardGroup>
