> 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.md). # sdm admin ```shell NAME: sdm admin - administrative commands USAGE: sdm admin command [command options] [arguments...] COMMANDS: approval-workflows-multistep, af manage approval workflows, approval steps, and approvers clouds manage clouds clusters manage clusters connectors, connector manage discovery connectors groups manage groups healthchecks manage healthchecks identities, identity manage identities kubernetes, k8s manage Kubernetes cluster managedsecrets, managedsecrets manage secrets network manage network nodes, relay, relays, node manage nodes organization manage organization settings policies manage policies ports manage port overrides rdp manage RDP servers resources manage resources rest make custom HTTP REST requests roles manage roles secretengines, secretengines manage secret engines secretstores, secretstore manage secret stores servers manage servers services, svc, service manage service accounts ssh manage SSH public key servers tokens, token manage admin tokens and api keys users manage users websites, web, http manage websites workflows, workflow manage workflows 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.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.