> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dify.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage Members

> Add teammates to your workspace and manage the roles that control their access

Workspace members are added and managed in **Settings** > **Members**. Each member's access is determined by the role they hold.

## Roles

There are four built-in roles:

* **Owner**: Full control of the workspace. One per workspace.
* **Admin**: Manage members and model providers, plus everything an Editor can do.
* **Editor**: Create, edit, and delete apps and knowledge bases.
* **Normal**: Use published apps only.

<Info>
  The Owner, Admin, and Editor roles can *create* knowledge bases, while who can *see and use* an existing one is controlled in its own settings. See [Manage Knowledge Settings](/en/self-host/use-dify/knowledge/manage-knowledge/introduction) for details.
</Info>

<Tip>
  On Dify Enterprise, you can create custom roles and grant members granular access to apps and knowledge bases. [**Contact sales**](https://udify.app/chat/QuwcpW1oBNcfeL55) to learn more.
</Tip>

## Add Members

The Owner and Admins can add members.

<Note>
  **Prerequisites:**

  * Set `CONSOLE_WEB_URL` to an address invitees can reach, not `localhost`. Every invitation link is built from it.
  * Configure an email service with `MAIL_TYPE` so Dify can email invitations.
    See [`CONSOLE_WEB_URL`](/en/self-host/deploy/configuration/environments#console_web_url) and [Mail Configuration](/en/self-host/deploy/configuration/environments#mail-configuration) for details.
</Note>

Select **Add**, enter one or more email addresses, choose a role, and send the invitation. An invitation link will be emailed to each address. The links also appear in the **Invitation sent** dialog, where you can copy and share directly.

Invitation links expire after 72 hours by default (configurable via `INVITE_EXPIRY_HOURS`); if someone doesn't accept in time, invite again to send a fresh link.

## Manage Members

**Change a role:** The Owner and Admins can change any member's role, and it takes effect on the member's next action, even if they're currently signed in. The Owner's role can only be changed through an ownership transfer.

**Remove a member:** The Owner and Admins can remove any member. This revokes the member's workspace access right away. The apps and knowledge bases they created stay in the workspace. The Owner can't be removed.

**Transfer ownership:** Only the Owner can transfer ownership. The transfer is confirmed with a verification code emailed to the Owner. Once verified, the chosen member becomes the new Owner and the previous Owner becomes an Admin.

<Note>
  Because the verification code is sent by email, ownership transfer requires a configured email service (`MAIL_TYPE`). See [Mail Configuration](/en/self-host/deploy/configuration/environments#mail-configuration) for details.
</Note>

## Troubleshooting

| Symptom                                                 | What to check                                                                                                                                      |
| :------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------- |
| Invitees don't receive the invitation email             | Email is sent only when `MAIL_TYPE` is configured. The invitation link can also be copied from the **Invitation sent** dialog and shared directly. |
| An invitation link won't open, or points to `localhost` | Every link is built from `CONSOLE_WEB_URL`. Set it to an address invitees can reach.                                                               |
| An invitation link has expired                          | Links last 72 hours by default. Invite the same email again to issue a new one.                                                                    |
| Ownership transfer never sends a code                   | The code is emailed to the Owner, so `MAIL_TYPE` must be configured.                                                                               |