> 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/kubernetes-rbac/create-rolebinding.md).

# Create Rolebinding

A RoleBinding assigns an existing group of users or users to a Role within a namespace for a cluster. Follow the steps given below to create a Role, through the Platform9 Clarity UI.

1. Navigate to Kubernetes>RBAC>RoleBindings.
2. Click New RoleBinding. A new window opens, providing an interface in which to enter info about the RoleBinding.

<figure><img src="https://351724846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHSO0ts94Xucvw1aQnUua%2Fuploads%2Fgit-blob-6f973d4d4d48f20ef40621c3e60b358e0f2b4634%2F2v4ociboua34resovx5ee59juzfhzb7bxi2hgkr4gttgxm4q9nmy2jgukdkncm41.png?alt=media" alt=""><figcaption></figcaption></figure>

3. Enter the Name for the RoleBinding.
4. Select the Cluster.
5. Select the Namespace.
6. Select the Role.
7. Select the checkboxes for the Users and/or Groups to which you wish to assign the Role.
8. Click Add Role Binding.

The RoleBinding is then created and visible within the Platform9 management UI under the list of existing RoleBindings. Once a RoleBinding is created, the users or groups of users that the Role has been assigned to, can perform operations specified in the Role.


---

# 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/kubernetes-rbac/create-rolebinding.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.