> For the complete documentation index, see [llms.txt](https://docs.deso.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deso.org/deso-backend/configuration/admins.md). # Admins Description of flags related to admin access on your node. ## Admin Public Keys `--admin-public-keys` Type: String\[] Default: \[] A list of public keys which gives users access to the admin panel. If '\*' is specified as a key, anyone can access the admin panel. You can add a space and a comment after every public key and leave a note about who the public key belongs to. Admins can add posts to the global feed, manage the whitelist/blacklist/graylists, among other admin functionality. ## Super Admin Public Keys `--super-admin-public-keys` Type: String\[] Default: \[] A list of public keys which gives users access to the super admin panel. If '\*' is specified as a key, anyone can access the super admin panel. You can add a space and a comment after every public key and leave a note about who the public key belongs to. Be careful who you grant Super Admin access to - Super admins can manage the reserve price at which you sell DESO, the fee you assess on DESO purchases, among other critical configurations. --- # 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.deso.org/deso-backend/configuration/admins.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.