> 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/settings/access/teams.md).

# Teams

Use Teams in Settings > Access > Teams to limit users to Action Pages with certain tags, and their data. Create Teams, add tags, assign users, and delete Teams.

**Teams** limit which Action Pages, and the data that comes from them, a user can see. A Team member only sees Action Pages that carry one of the Team's [Tags](/action-pages/action-page-basics/ap-tags.md), while their [permission set](/settings/access/permission-sets.md) controls what they can do. You manage Teams in **Settings > Access > Teams**. This article covers how Teams work, and how to create a Team, add tags, assign users, tag Action Pages, and delete a Team.

## Before You Begin

* Teams are available on accounts with Pro enabled. If **Teams** is marked as a Pro feature in your Settings menu, contact our Support team at <help@anedot.com>.
* To create, edit, or delete Teams and manage their tags, you need **Account Management: Edit Account Details and Configuration** permissions.
* To assign users to a Team, you need **Access Management: Edit Users** permissions.

## How Teams Work

* Users who aren't on a Team have full access to the account's Action Pages and data.
* A Team member sees only the Action Pages tagged with one of the Team's tags. This also limits the submissions, commitments, events, tickets, donations, and entries they see to those pages.
* Each Team gets a default tag with the Team's name when it's created. Renaming the Team renames its default tag.
* When a Team member creates a new Action Page, the Team's default tag is added to it.
* A user can be on one Team at a time.
* The **Owner** can't be assigned to a Team.

### Examples

* A consultant who should only see the pages they build for you.
* Volunteers who work on one campaign or event.
* A temporary event Team with only the event's pages tagged.

## Create A Team

To create a Team:

1. Go to **Settings > Access > Teams**.
2. Click **Create team**.
3. Enter a **Name**. Each Team name must be unique in your account.
4. (Optional) Enter a **Description**.
5. Click **Save team**.

The Team appears in the list with its default tag.

## Add Tags to a Team

A Team can include more tags than its default tag. Team members see Action Pages with any of the Team's tags.

To add or remove a tag:

1. Go to **Settings > Access > Teams**.
2. In the **Tags** column, click the pencil icon on the Team's row.
3. Select a tag to add it, or select a tag that's already on the Team to remove it.

The default tag can't be removed. To create, rename, recolor, or delete tags for your account, click **Tags** at the top of the Teams page, or **Manage tags** at the bottom of the tag list.

## Assign Users to a Team

First invite the user with the appropriate permission set. Once they've accepted the invite, assign them to a Team. See [Users](/settings/access/users.md).

To assign users from the Teams page:

1. Go to **Settings > Access > Teams**.
2. On the Team's row, click **Assign users**.
3. Select the users you want to add.
4. Click **Add** to save. The button shows how many users you selected.

You can also assign a Team to one user at a time:

1. Go to [**Settings > Access > Users**](/settings/access/users.md).
2. Click the user's name.
3. Under **Team assignment**, choose the Team.
4. Click **Save**.

## Tag Action Pages for a Team

Add the Team's tag to every Action Page the Team should see. See [Tags](/action-pages/action-page-basics/ap-tags.md) for the steps.

{% hint style="warning" %}
If no Action Pages have one of the Team's tags, Team members won't see any Action Pages or their data.
{% endhint %}

## Delete A Team

You can delete a Team only after everyone is removed from it. **Delete** is unavailable while the Team still has users.

To delete a Team:

1. Go to [**Settings > Access > Users**](/settings/access/users.md) and move each Team member to another Team or to no team.
2. Go to **Settings > Access > Teams**.
3. On the Team's row, click **Delete**.
4. Click **Delete team** to confirm.

{% hint style="danger" %}
This action cannot be undone.
{% endhint %}

## Related Articles

* [Users](/settings/access/users.md)
* [Permission Sets](/settings/access/permission-sets.md)
* [Tags](/action-pages/action-page-basics/ap-tags.md)
* [Manage Pages](/action-pages/action-page-basics/manage-pages.md)
* [Vendor & Client: Best Practices](/settings/access/vendor-client-best-practices.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/settings/access/teams.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.
