> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-kubernetes/5.7/security/creating-and-enabling-keystone-groups-and-user-associations.md).
# Creating And Enabling Keystone Groups And User Associations
## Introduction
In this article, we describe the features included in the UI, which allow administrators to create groups of local users. These features are located under the Tenants and Users dashboard, within the Admin Settings. With this solution, users can create a named group, assign them access to a specific tenant and region, providing access as an Admin, Self Service or Read only subscriber. To access these settings, click on the username in the upper-right hand corner, then click on **Admin Settings**.
## Groups
Once in the Admin Settings area, go to the *Tenants and Users* tab to view and edit the Tenants, Users and Groups.
Navigate to the Groups tab and click on the New Group button.
On the Add New Group page, enter a Name, Description, Tenant and Role access. Next, define what Tenants this Group will be able to access, and what role those users will be assigned to within each Tenant. Once complete, click Save. The users in that group can now access the Platform9 services and control cluster access as noted in the Kubernetes RBAC Policies.
{% hint style="info" %}
**Note**
Admins should only assign a user to a unique group. If a user belongs to multiple groups, they will automatically be granted the privileges associated with each group.
{% endhint %}
If you have questions regarding this setup, reach out to our [Support Team](https://platform9.zendesk.com/hc/en-us/requests/new?ticket_form_id=360000924873) for further assistance.
---
# 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.platform9.com/managed-kubernetes/5.7/security/creating-and-enabling-keystone-groups-and-user-associations.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.
