> 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/groups.md).

# Groups

A **Group** is a collection of permissions that defines the level of access for users belonging to it. Groups consist of:

* Namespaces
* Application permissions
* Administration permissions

Groups must be pre-created, and the group's names in Lenses must match (case sensitive) those in the SSO provider.

## Creating groups

To create a new Group, go to **`Admin->Groups->New Group.`**

For every Group, you must set the data namespaces for Kafka or other available connections to data sources.

Groups must be given names, optionally a description.

## Adding namespaces to groups

Namespace permissions define the access to datasets. and

Each group must have a namespace. A namespace is a set of permissions that apply to topics or a set of topics, for example, ***prod\****. This allows you to define virtual multi-tenancy.

## Adding application permissions

Application permissions define how a user can interact with applications and linked resources associated with those datasets.

Application permissions cover:

1. Viewing or resetting Consumer group offsets linked to a group's namespaces
2. Deploying or viewing connectors linked to a group's namespaces
3. Deploying or viewing SQL Processors linked to a group's namespaces

Additionally, application permissions define whether a group can access a specified Connect cluster.

## Adding administration permissions

Admin permissions refer to activities that are in the global scope of Lenses and affect all the related entities.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lenses.io/latest/devx/5.5/deployment/configuration/iam/groups.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.