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

# Members and invitations

Admins invite teammates and manage roles from the workspace's **Members** page.

## Invite teammates

1. Select **Add teammates**.
2. Enter their work emails and choose the intended role.
3. Send the invitations, or use the invitation's **Copy** action to share its link.
4. Review the **Invited** list until the teammates accept.
5. Add accepted members to the relevant teams or queues.

For a larger team, use **Upload CSV** or **Pick from Salesforce / HubSpot** when available. Check the proposed people and roles before sending; importing identities does not connect their calendars.

## Finish member setup

Each member connects their calendar and sets their hours. Use the calendar nudge controls to remind members whose calendars are missing. An admin may review member settings, but should confirm the actual calendar account with the teammate.

Use [Connected identities](/settings/identities.md) for CRM owners, Slack and sequencing senders. These mappings are separate from the email used to invite the teammate.

## Change access

Edit the member's role when their responsibilities change. Account owners retain admin access. Removing a member affects future access; review queue membership, workflows and host settings that depend on them before removal.

See [Roles and sharing](/settings/roles-and-sharing.md) and send new teammates the [Member setup guide](/get-started/member-setup.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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/settings/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 `build a script that syncs our docs to a CMS` 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.