> For the complete documentation index, see [llms.txt](https://cc.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc.docs.landis.cloud/administration/users.md).

# Users

This is where you enabled Azure AD users for contact center.

Navigate to Configuration | Users | Edit

{% tabs %}
{% tab title="User Information" %}

| Setting               | Description                                                                       |
| --------------------- | --------------------------------------------------------------------------------- |
| Name                  | Name of user                                                                      |
| Surname               | Surname of user                                                                   |
| Email Address         | Email address of user                                                             |
| Phone Number          | Phone number of user                                                              |
| Username              | Username of user                                                                  |
| Public display name   | Agent's name displayed to external chat users                                     |
| Send Activation Email | Sends contact center activation email to user                                     |
| Active                | If enabled, user can log into Contact center.  If disabled, user is denied access |
| Lockout enabled       | Enables password lockout policy                                                   |
| {% endtab %}          |                                                                                   |

{% tab title="Roles" %}
Default roles are Admin, Manager, and User.  The role specifies what part of the application the user can access. See [Roles](/administration/roles.md)

{% hint style="info" %}
Additional roles can be created to suite your particular needs.
{% endhint %}
{% endtab %}

{% tab title="Contact Center Settings" %}

| Settings                   | Description                                                                                                                            |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Direct Call Records Groups | Object where the users direct call records are stored. See [Direct Call Records Groups](/administration/direct-call-records-groups.md) |
| {% endtab %}               |                                                                                                                                        |

{% tab title="Queues" %}
Select the checkbox beside a queue to assign the user as an agent for that queue. A user can be assigned to multiple queues.

Skills queues will not be available to assign to the user in this list. Use the skills tab.
{% endtab %}

{% tab title="Skills" %}
See [Skills based Routing](/appendix/skills-based-routing.md)
{% endtab %}

{% tab title="Organization Units" %}
View OU permissions for the user. See [Organization Units](/administration/organizational-units.md)
{% endtab %}
{% endtabs %}


---

# 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://cc.docs.landis.cloud/administration/users.md?ask=<question>&goal=<user_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.