> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/account-settings/managing-your-team.md).

# Managing Your Team

Invite and remove members of your team from your account settings.

## Adding Users

To add a new member to your team, go to the `Team` tab in your `Account Settings` page. From there, click the `Invite Team` button, which will open a modal allowing you to enter the email addresses of team members to invite.

While inviting teammates, you'll also be able to configure their [roles & permissions](/platform/account-settings/permissions-and-user-groups.md) before sending out the invites.

Once you've invited them, they'll receive an invite email to join your team directly in their inbox.

If the user you're looking to invite already has an account, they'll receive a notification to join your team once they've logged in. They have the option of accepting or declining the invite request.

### **Bulk Invite Flow**

For inviting multiple teammates at once, you will be able to use CSV upload:

1. In the `Invite Team` modal, click the `Bulk CSV Invite` button.
2. Upload a CSV file structured as described below.
3. The system will validate the CSV and display any errors.
4. If the CSV is valid, you can proceed to send the invites.

#### CSV Structure for Bulk Invites

Your CSV file should include the following columns:

* Required:
  * Email: The email address of the user to invite
  * Role: The role to assign (Admin, Editor, or Viewer)
* Optional:
  * First Name: The user's first name
  * Last Name: The user's last name
  * User Groups: Comma-separated list of [user group names](/platform/account-settings/permissions-and-user-groups.md)
  * Custom Attributes: Any [custom attributes](/platform/account-settings/account-attributes.md) defined in your organization

An example CSV where GroupA, Group B and Group C are predefined User Groups and Location is a predefined Custom Attribute. (Unknown User Groups or Custom Attributes will be skipped)

| Email           | Role   | First Name | Last Name | User Groups          | Location    |
| --------------- | ------ | ---------- | --------- | -------------------- | ----------- |
| <john@test.com> | Admin  | John       | Doe       | GroupA,GroupB,GroupC | Los Angeles |
| <jane@test.com> | Viewer | Jane       | Doe       | GroupA               | Singapore   |

## Removing Users

From the same page, you can also remove members from your team. Click the trash can icon next to their name to remove them.


---

# 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.feathery.io/platform/account-settings/managing-your-team.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.