> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/devx/5.5/deployment/configuration/iam/users.md).
# Users
This page describes managing users in Lenses.
Users must be assigned to a group. SSO and LDAP users are mapped to a group matching the group name provided by the Idp.
{% hint style="warning" %}
Group name matching is case-sensitive.
{% endhint %}
Multiple types of users can be supported at the same time.
## Adding a user with Basic Authentication
Select `Admin->Users->New User->Basic Auth`.
## Mapping SSO users to groups
By default, users are mapped to the group provided by the SSO provider. If you wish to override the group mapping from your SSO, users can be created directly in Lenses and you can manually map the user to a group.
## Mapping LDAP users to groups
By default, users are mapped to the group provided by the LDAP server. If you wish to override the group mapping you manually map the user to a group.
See [LDAP user group mapping](/latest/devx/5.5/deployment/configuration/iam/authentication/ldap.md#ldap-user-group-mapping).
## Listing Users
Lenses allows you to view users and:
1. Authentication type
2. Groups they belong to
3. Last login
Go to `Admin -> Users.`
---
# 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.lenses.io/latest/devx/5.5/deployment/configuration/iam/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.