> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/integration-hub/creating-users.md).
# Creating Users
Add new Pandium users by going to Settings → Users, entering their name, email, organization, and letting them activate access via an emailed login and password update link.
To add a new user to Pandium, navigate to “Settings” in the navigation sidebar, then “Users” in the top bar within the Settings resource.
Navigate to the Users tab, and click the “Add New User” button near the top right to access the user creation page.
Add in the new user's details: Name, email address, and organization. For all non-partner users, the organization will be the name of your company. You can also directly add users to your partner organizations by selecting them from the dropdown.
After creation, the newly added user will receive an email from Pandium prompting them to login to Pandium and update their password.
Congratulations! You have successfully added a user.
---
# 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.pandium.com/integration-hub/creating-users.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.
