> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/docs/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/docs/hub/settings.md).
# Settings
This page describes how to manage team members/users and notifications.
### Client Settings
In this section, the client can see their Company name and Partner ID, configure email notifications, and review the Terms of Service.
### Notification Settings
By clicking this button, the notification settings can be found
There are multiple categories of email notifications. You can choose which one to receive.
{% hint style="info" %}
Choosing the right notification is enough. The setting will be automatically changed.
{% endhint %}
### Users
There are two available roles: **Owner** and **Member.**
Each role has different permissions.
{% hint style="info" %}
Only owners can manage users (add, edit, or delete) and can perform number migration.
{% endhint %}
### How to add new users
{% stepper %}
{% step %}
In the Settings section, click Invite user
{% endstep %}
{% step %}
Fill in the Email and Full Name, and choose the role. Click Send Invite.
{% endstep %}
{% step %}
The invited user will receive an email to accept and create a password.
{% endstep %}
{% endstepper %}
### How to manage existing users
{% stepper %}
{% step %}
In the Settings section, click on the user.
{% endstep %}
{% step %}
It is possible to update the role or delete the user. Both options are available only for owners.
{% endstep %}
{% endstepper %}
---
# 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/docs/hub/settings.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.
