> 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/6.0/user-guide/iam/users.md).
# Users
This page describes Users in Lenses.
{% hint style="info" %}
Users are assigned to groups. The groups inherit permissions from the roles assigned to the groups.
{% endhint %}
User can be manually created in Lenses. Users can either be of type:
1. SSO, or
2. Basic Authentication
When creating a User, you can assign them groups membership.
Each user, once logged in can update their Name, Profile Photo and set an email address.
{% hint style="info" %}
For SSO, your SSO email is still required to login
{% endhint %}
## Create a User
To Create Service Account go to **IAM->Users->New User,** once created you can assign the user to a group.
IAM Users
You can also manage Users via the CLI and YAML, for integration in your CI/CD pipelines.
{% code title="terminal" %}
```bash
➜ lenses users
Usage:
lenses users [command]
Aliases:
users, usr, u
Available Commands:
create Creates a new user.
delete Deletes a user.
get Returns a specific user
get-current Returns the currently authenticated user
list Returns all users
metadata Manages user metadata.
set-groups Assigns the given user exactly to the provided groups, ensuring they are not part of any other groups.
update Updates a user.
update-profile Allows updating fields of the user profile.
```
{% endcode %}
---
# 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/6.0/user-guide/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.
