> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/references/cli/admin/roles.md).

# sdm admin roles

```shell
NAME:
   sdm admin roles - manage roles

USAGE:
   sdm admin roles command [command options] [arguments...]

COMMANDS:
   list         list all roles in your organization
   add, create  add a new role
   update       update a role's name or tags
   delete       delete a role by name or ID
   grant        grant one or more roles access to a datasource by name, or to a group of datasources by filter
   revoke       remove access from one or more roles to a datasource by name, or to a group of datasources by filter
   grant-all                 grant access to all datasources to a role
   revoke-all                revoke access to all datasources from a role
   granted-entitlements      list resources granted through a role
   requestable-entitlements  list resources requestable through a role

OPTIONS:
   --help, -h  show help
```


---

# 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.strongdm.com/references/cli/admin/roles.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.
