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

# sdm admin users

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

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

COMMANDS:
   list             list all users in your organization
   add, create      add a new user
   assign, attach   attach a set of users to a role
   suspend          suspend a user by email address
   reinstate        reinstate a user by email address and role
   grant-temporary  grant temporary datasource access to a user
   revoke           revoke user access from a datasource by name, or from a group of datasources by filter
   update           update users in your organization
   revoke-all                revoke access from all datasources to a user
   delete                    delete users by email or id
   granted-entitlements      list resources granted to a user
   requestable-entitlements  list resources requestable by a user

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/users.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.
