> 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.14/clusters/kubernetes-rbac/create-role.md).
# Create Role
A Role is a set of permissions that can be assigned to a user within a namespace for a cluster. A namespace divides a cluster between multiple users. Kubernetes APIs are categorized into API groups, based on the API objects that they relate to. The API groups for Kubernetes that are visible on the Platform9 Clarity UI consist of upstream Kubernetes APIs and Kubernetes APIs provided by Platform9.
While creating a Role, you can specify the operations that can be performed by the Role on one or more API objects in one or more API groups. You can create one or more Kubernetes Roles for a namespace through the Platform9 Clarity UI. You can also set permissions on operations related to one or more API groups, when you create a new role.
Follow the steps given below to create a Role, through the Platform9 Clarity UI.
1. Navigate to Kubernetes>RBAC>Roles.
Click Add Role.
3. Enter the Name for the cluster.
4. Select the Cluster.
5. Select the namespace for which you want to create the Role.
6. Search or select an API group and select the operations to grant permissions on operations for the selected API group. Repeat selection of operations on as many other API groups as required. To grant permission of a specific verb to add to the resource, select the checkbox for the specific operation.
7. When complete, click the *Add Role* button.
A Role is created and visible in the Platform9 management plane under the list of existing Roles. Once a Role is created, you can assign the Role to a user or group of Users by creating a RoleBinding.
---
# 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.14/clusters/kubernetes-rbac/create-role.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.
