> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/managing-teams/inviting-members.md).
# Inviting Members
### Select Members from the Admin Console
You can access the [Admin Console](/platform-overview/admin-console.md) at app.pixiebrix.com. Make sure the desired team is selected at the top.
Click Members on the left side nav.
### Invite and assign a role
Click the **Invite** button in the top right, then input the new teammate's email addresses, assign roles, and click **Invite Team Members**.
{% hint style="info" %}
You can change a member's role later if needed. Learn more about [Roles](/managing-teams/access-control/roles.md).
{% endhint %}
### Add more or click Invite Team Members
You can add more by clicking the **Add Invite** button below the input fields.
Once you've added as many members as you'd like click the Invite Team Members Button.
### Automatic Team Enrollment / Domain Capture
{% hint style="info" %}
Domain capture is only available on the Enterprise plan.
{% endhint %}
PixieBrix can be configured to automatically associate users with a given email domain(s) with your team. Team members can automatically added with one of two roles:
* Member
* Restricted
To enable automatic enrollment for your organization, contact
---
# 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.pixiebrix.com/managing-teams/inviting-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.
