> 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.1/user-guide/iam.md).

# Identity & Access Management

This page describes Identity & Access Management (IAM) in Lenses.

IAM controls what users and service accounts can do in Lenses. Permissions flow from **principals → groups → roles → policies**. If any policy statement matches with `effect: deny`, access is denied.

### Common setup flow

{% stepper %}
{% step %}

### Configure authentication

Pick Basic Auth or SSO/SAML.
{% endstep %}

{% step %}

### Create roles and policies

Define actions, resources, and `allow`/`deny`.
{% endstep %}

{% step %}

### Create groups and assign roles

Attach one or more roles to each group.
{% endstep %}

{% step %}

### Add users and service accounts to groups

Membership drives permissions.
{% endstep %}

{% step %}

### Validate access

Log in as a user and check expected visibility and actions.
{% endstep %}
{% endstepper %}

<table data-view="cards"><thead><tr><th>Topic</th><th>Description</th><th data-hidden data-card-target data-type="content-ref">Link</th></tr></thead><tbody><tr><td><strong>Overview</strong></td><td>Core concepts and policy evaluation</td><td><a href="/latest/devx/6.1/user-guide/iam/overview.md">Overview</a></td></tr><tr><td><strong>Authentication</strong></td><td>Basic Auth, SSO/SAML, and admin accounts</td><td><a href="/latest/devx/6.1/deployment/configuration/authentication.md">Authentication</a></td></tr><tr><td><strong>Users</strong></td><td>Create users and manage group membership</td><td><a href="/latest/devx/6.1/user-guide/iam/users.md">Users</a></td></tr><tr><td><strong>Service Accounts</strong></td><td>Programmatic access via service account tokens</td><td><a href="/latest/devx/6.1/user-guide/iam/service-accounts.md">Service Accounts</a></td></tr><tr><td><strong>Groups</strong></td><td>Collect principals and grant roles</td><td><a href="/latest/devx/6.1/user-guide/iam/groups.md">Groups</a></td></tr><tr><td><strong>Roles</strong></td><td>Create roles and attach policies</td><td><a href="/latest/devx/6.1/user-guide/iam/roles.md">Roles</a></td></tr><tr><td><strong>IAM Reference</strong></td><td>All actions and resource formats</td><td><a href="/latest/devx/6.1/user-guide/iam/iam-reference.md">IAM Reference</a></td></tr><tr><td><strong>Example Policies</strong></td><td>Ready-to-use role templates</td><td><a href="/latest/devx/6.1/user-guide/iam/example-policies.md">Example Policies</a></td></tr></tbody></table>


---

# 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.1/user-guide/iam.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.