> For the complete documentation index, see [llms.txt](https://help.citrusad.com/retail-media-interface/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.citrusad.com/retail-media-interface/advertiser-team-and-user-management/managing-teams.md).

# Managing teams

In the **Teams** page, you can:

* Filter teams
* Edit any team you have access to
* Add and remove users
* Manage email notifications (coming soon)

You can view all teams you can access. Retailers can see all teams in their platform.

The **Team Manager** table displays each team, company name, number of users, and, if a marketplace is integrated. the seller ID is shown.

#### **How to manage teams:**

1. Access **Teams** from the side menu. Retailers will see it in the main menu; advertisers will find it under **Settings**.
2. Filter to the team you want to manage. Use the filter to search for a team; your current team always appears at the top before filtering.
3. Click the team's name to open the team. Alternatively, if you want to add users or edit the team's setting, click the ellipsis.
4. Alternatively, if you want to add users or edit the team's setting, click the ellipsis.

{% hint style="info" %}
You can also export a list of teams to CSV if required.
{% endhint %}

#### Guided tour

Take a guided tour below to see step-by-step how easy it is:

{% embed url="<https://epsilon.storylane.io/share/1notzwc0nkgw>" fullWidth="true" %}


---

# 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://help.citrusad.com/retail-media-interface/advertiser-team-and-user-management/managing-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.
