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

# Team & Organization

Manage your organization settings and team members from the side menu.

***

## Organization Info

Open the side menu (hamburger icon, top-left) and go to **My Organization**.

<figure><img src="https://1428241958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMzhwr2nXLtM9EytX9Xvg%2Fuploads%2Fgit-blob-8250621c4b249f30e4a8fb0e86bf8c29e56c047a%2Fscreenshot-team-organization.png?alt=media" alt=""><figcaption><p>Organization settings</p></figcaption></figure>

Here you can:

* View and update your **organization name**

***

## Team Members

The Members section shows all members and a seats counter (e.g. *"100,000 seats available including 0 managers"*). Each row contains:

| Column       | Description                                                |
| ------------ | ---------------------------------------------------------- |
| **Name**     | Display name                                               |
| **Email**    | Login email                                                |
| **Verified** | Whether the user confirmed their email                     |
| **Role**     | Admin or Member                                            |
| **Manager**  | The user's manager (set when inviting or editing a member) |

### Adding Members

Click **+ Add new member** to invite someone by email. The dialog asks for:

1. **Email**
2. A **Role** — `Admin` or `Member` (with a one-line description of what each can do)
3. If you pick `Member`, an optional **Manager** dropdown to assign their manager from existing members

The invitee receives an email invitation to join your organization.

### Roles

| Role        | Capabilities                                                                                                                                                                                                                                       |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Admin**   | Full access: manage team, organization settings, data sources, billing, lenses                                                                                                                                                                     |
| **Member**  | Use Leadbay: discover, like, enrich, export, activate. Cannot manage org settings or billing                                                                                                                                                       |
| **Manager** | A Member who is the manager of one or more other members. Gets visibility into their reports' activity in the [Manager Dashboard](/doc/product-guides/manager-dashboard.md). Doesn't change app permissions — only changes who shows up under whom |

Use the action menu (three dots) on each row to change a member's role, set/change their manager, or remove them.

{% hint style="info" %}
Only admins can import data, manage billing, and change organization settings.
{% endhint %}


---

# 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.leadbay.app/doc/product-guides/team-management.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.
