> For the complete documentation index, see [llms.txt](https://docs.tesseract.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tesseract.fi/earn-direct-and-earn-api/earn-direct/organizations/team-management.md).

# Team Management

Admins manage their [organization's](/earn-direct-and-earn-api/earn-direct/organizations.md) team — inviting members, assigning roles, and controlling access.

### Inviting members

Admins invite members by email. The invitee receives a link, authenticates, and joins the organization with the role chosen at invite time. Invites expire after **7 days** and can be revoked or resent. Membership is always explicit — there is no email-domain auto-join.

If the organization is already `active`, invited members are cleared to transact as soon as they accept.

### Roles & permissions

Every member has exactly one role, and permissions derive from that role.

| Role                     | What they can do                                                    |
| ------------------------ | ------------------------------------------------------------------- |
| **Admin**                | Full control — manage the team, run KYB, and perform all operations |
| **Withdrawals Manager**  | Create deposits and submit withdrawals                              |
| **Whitelisting Manager** | Whitelist withdrawal addresses and create deposits                  |
| **Viewer**               | Read-only access to portfolio, reports, and activity                |

Key boundaries:

* Only **admins** invite members, change roles, suspend members, and run KYB.
* Verifying (whitelisting) an address requires the **Whitelisting Manager** (or admin) role.
* Submitting a withdrawal requires the **Withdrawals Manager** (or admin) role.
* The two manager roles are separate: a Whitelisting Manager cannot submit withdrawals, and a Withdrawals Manager cannot verify addresses. Both can create deposits.

### Member lifecycle

Admins can change a member's role or **suspend** a member; suspension takes effect on the member's next request and can be reversed by reactivating them. Admins can also change another admin's role — including downgrading an admin to a more restrictive role. Admins cannot suspend themselves or change their own role.

### Wallet verification

Before the organization can withdraw to an external address, that address must be **verified** (whitelisted). A **Whitelisting Manager** or admin submits the address; it is screened through Tesseract's compliance checks (travel rule and wallet risk screening) and becomes available for withdrawals once approved. Until then it stays on hold. Verified addresses are shared across the organization.

Once verified, wallets can be managed — changing which wallet receives a product's withdrawals (**Admin**-only), or retiring one you no longer use (**Whitelisting Manager** or **Admin**). See [Managing Whitelisted Wallets](/earn-direct-and-earn-api/earn-direct/organizations/managing-whitelisted-wallets.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tesseract.fi/earn-direct-and-earn-api/earn-direct/organizations/team-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.