> 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 and Assign Tags within the Action Pages Index to manage and organize Actions Pages and scope user access.

**Create** and **Assign Tags** within the Action Pages Index to manage and organize Actions Pages and scope user access.

## Create Tags

To **Create Tags**, follow the steps below:

1. Access the **Action Pages → Pages** tab within your fundraising account.
2. Click the **Tags** icon in the upper right corner of the Action Pages Index.
3. Click **+ Create new tag**.
4. **Name** the Tag.
5. *Optionally*, click the **Note** icon to add a Tag Description.
6. *Optionally*, click on the **Color** to assign a specific color to the Tag.
7. Click your cursor out of the Tag field to **Save** the Tag.

## Assign Tags

To **Assign Tags** to an Action Page, follow the steps below:

1. Access the **Action Pages → Pages** tab within your fundraising account.
2. Hover over the **Tags** column to the right of the Action Page.
3. Click the **Pencil** icon.
4. From the list of Tags, select the **Tag(s)** you would like to assign to the Action Page.
5. Click your cursor off of the list of Tags to **Save** the assignment.

***Team Tags** will show a **People** icon to the right of the Tag name. These Tags limit a user's access to the fundraising account data. The Team Tag should only be assigned to grant user access to the Action Page and associated data. If a Team Tag is not assigned to any Action Pages, users assigned to the Team will not have access to any account data.*

## Filter Action Pages by Tags

To **Filter** Action Pages by Tags, follow the steps below:

1. Access the **Action Pages → Pages** tab within your fundraising account.
2. Click the **Filter** menu button.
3. Select the **Tags** you would like to filter by.
4. Click **Apply Filters**.
5. Click **X** in the upper right corner to close the Filter Drawer.

## Related

* [Donor Covers Fees](/action-pages/advanced-features/donor-covers-fees.md)
* [Manage Events](/action-pages/action-page-basics/manage-events.md)
* [Goals](/action-pages/advanced-features/goals.md)
* [Share an Action Page](/action-pages/action-page-basics/share-an-action-page.md)
* [New Jersey Public Financing Page Setup](/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.