> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/settings/workspace-settings/members.md).
# Members
Open **Settings → Members** to see workspace members and pending invitations. Search by name or email, or choose **Members** or **Pending invites** to narrow the table.
Workspace admins manage invitations and roles. The table also shows each member’s CRM mapping, calendar connection, and conferencing setup.
## Invite people
Click **Invite Member** or the header’s **Invite members** button. Enter an email address and choose **Member** or **Admin** for that person. Use **Add new member** to add more rows, then review the addresses and roles before clicking **Send invitations**.
You can invite up to 50 people at once. If an address or role needs correcting, fix the highlighted rows before sending. Use **Pending invites** to track invitations and find the available follow-up actions.
## Help a member get ready
If a member has no connected calendar, use **Send reminder** in their Calendar column to email them a connection reminder. A reminder can be sent once every 24 hours. The table shows **Reminder sent** after it is sent.
Open the member’s action menu and choose **Edit** to manage their role, or **Manage User Preferences** to review their timezone, weekly hours, and vacation coverage. See [Member availability](/settings/workspace-settings/members/managing-member-availability.md).
Ask members to connect their calendar and check their hours before including them in live routing. Being a workspace member does not automatically give someone access to every sales handoff; review the router’s allowed bookers separately.
---
# 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://help.distro.so/settings/workspace-settings/members.md?ask=&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.
