> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/action-pages/action-page-basics/ap-tags.md).

# Tags

Create, edit, and delete tags, add tags to Action Pages, and filter the Action Pages list by tag in Anedot to organize your pages and control Team access.

**Tags** help you organize your Action Pages and control which pages Team members can see. You manage them from **Action Pages > Action Pages**. This article covers how to create and manage tags, add tags to a page, and filter pages by tag.

## Before You Begin

* To create, edit, or add tags, you need **Action Pages: Edit permissions**.
* Each Team has its own tag. Team members only see Action Pages that carry their Team's tag. See [Teams](https://docs.anedot.com/settings/access/teams.md).

## Create And Manage Tags

To create a tag:

1. Go to **Action Pages > Action Pages**.
2. Click **Manage tags**.
3. Click **New tag**.
4. Enter a **Tag name**.
5. (Optional) Enter a **Description**.
6. (Optional) Choose a color.
7. Click **Save**.

The tag is saved and available to add to any Action Page. To finish, click **Done**.

In **Manage tags**, you can also rename a tag, change its description or color, or delete it. Team tags show a **Team** badge and can't be renamed here.

## Add Tags to a Page

To add or remove tags on a page:

1. Go to **Action Pages > Action Pages**.
2. On the page's row, click the pencil in the **Tags** column.
3. Select a tag to add it, or select a checked tag to remove it.

The page's tags update right away. To create a new tag from this list, type its name in **Filter tags** and select **Create "\[name]"**.

{% hint style="warning" %}
Adding or removing a Team tag changes which Team members can see the page and its data. If a Team's tag isn't on any Action Pages, members of that Team won't see any pages.
{% endhint %}

## Filter Pages by Tag

To filter the Action Pages list by tag:

1. Go to **Action Pages > Action Pages**.
2. Click the filter button.
3. Under **Access tags**, select the tags to filter by.

The list shows the pages that carry the selected tags.

## Related Articles

* [Teams](https://docs.anedot.com/settings/access/teams.md)
* [Manage Pages](https://docs.anedot.com/action-pages/action-page-basics/manage-pages.md)
* [Donor Covers Fees](https://docs.anedot.com/action-pages/advanced-features/donor-covers-fees.md)
* [Manage Events](https://docs.anedot.com/action-pages/action-page-basics/manage-events.md)
* [Goals](https://docs.anedot.com/action-pages/advanced-features/goals.md)
* [Share An Action Page](https://docs.anedot.com/action-pages/action-page-basics/share-an-action-page.md)
* [New Jersey Public Financing Page Setup](https://docs.anedot.com/action-pages/state-specific-pages/new-jersey-public-financing-page-setup.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.anedot.com/action-pages/action-page-basics/ap-tags.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
