> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/partner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/partner/partner-hub/users.md).
# Users
This page describes how to manage Partner team members / users.
There are two available roles: **Partner Owner** and **Partner Member.**
{% hint style="info" %}
**Only Partner Owners** can manage Users, which includes adding, editing, or deleting users.
{% endhint %}
### How to add new users
{% stepper %}
{% step %}
Navigate to **Settings > Team > Invite user**\
\
{% endstep %}
{% step %}
Receive the OTP via email and enter.
{% endstep %}
{% step %}
The invited user will receive an email to accept and create a password.
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
**Account Sharing Not Recommended**
For security and auditability, each person accessing a Partner Account should be provisioned with individual login credentials and assigned the appropriate role (Owner or Member).
Accessing a Partner Account using shared credentials is not recommended as it increases the risk of unauthorised access and obscures the audit trail. 360dialog is not liable for any loss or damages arising from authorised or unauthorised access resulting from shared credentials or API keys.
{% endhint %}
---
# 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.360dialog.com/partner/partner-hub/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.
