> For the complete documentation index, see [llms.txt](https://docs.lumi-ai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumi-ai.com/product-features/organization-settings/members.md).
# Members
All members defined for the organization can be found in the Members section of Organization Settings.
## Overview
The **Members** section in Lumi AI allows administrators to manage user access within an organization. This includes adding and removing users, assigning roles (Admin, User), and adjusting knowledge base access.
#### Accessing the Members Page
To access the **Members** page:
1. Navigate to **Settings** in the left sidebar.
2. Click on the **Members** tab under **Admin Settings**.
### Managing User Roles
Members in Lumi AI can be assigned different roles:
* **Admin**: Full permissions, including managing users, modifying settings, and accessing all knowledge bases.
* **User**: Belongs to the user data base.
### Inviting New Users
New users can be invited to the organization so long as there are seats available.
1. Click the **+ Invite** button in the top right corner.
2. Enter the user’s email address.
3. Assign a **role** (Admin/User).
4. Send the invitation.
---
# 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.lumi-ai.com/product-features/organization-settings/members.md?ask=&goal=
```
`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.