> For the complete documentation index, see [llms.txt](https://docs.noros.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.noros.ai/account-management/team-members.md).

# Team Members

Noros supports multi-user access so your team can collaborate on cloud operations. Manage team members and seats from **Settings > Team Members**.

### Inviting Team Members

1. Go to **Settings > Team Members**.
2. Enter the email address of the person you'd like to invite.
3. Click **Invite**.

The invited team member will receive an email with instructions to create their Noros account or sign in.

#### Domain Restriction

You can only invite users whose email address matches your organization's domain. For example, if your account is registered under `@acme.com`, you can only invite other `@acme.com` email addresses.

### Seat Management

The number of seats included depends on your plan. See the [Noros pricing page](https://www.noros.ai/pricing) for the seats each plan includes.

#### Adding Seats

If you need more seats than your plan includes:

1. Go to **Settings > Team Members**.
2. Add a seat, which will adjust your monthly billing accordingly.
3. Invite the new team member.

#### Removing Seats

To remove a seat:

1. Go to **Settings > Team Members**.
2. Remove or unassign the team member.
3. The seat adjustment will be reflected in your next billing cycle.

### Managing Team Members

From the Team Members settings, you can:

* **View all members** — See who has access to your Noros account
* **Remove members** — Revoke a team member's access
* **Manage seats** — Add or remove available seats

### Access and Permissions

All team members within a Noros account share access to the connected cloud accounts. Each team member can query data from any connected account using the account switcher.


---

# 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.noros.ai/account-management/team-members.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.
