> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm/arm-administration/user-management/changing-super-admin-in-arm.md).
# Changing Super Admin in ARM
We are thrilled to announce that you can easily change your Super Admin with our new 23.1 release.
With the new 23.1 release, we’ve consolidated the roles of Super Admin and Registered Admin into a single empowered Admin role. But also with the new 23.1 release, we have added a new feature so you can assign the ex-Super Admin from your login.
Please follow the simple steps below, making sure you are on the latest 23.1 build.
1. Log in with your Admin credentials. Go to the Users section in the Admin panel.
2. From the User tab, you will see the \* symbol next to the current Super Admin name. Click on the Edit icon.
3. Edit the previous Super Admin user, remove the Admin access by pressing the 'Deactivate' button on the right.
4. Once the deactivation is completed, you will see the other Admin being promoted to Super Admin.
5. Once you're finished, save the changes. You will get a confirmation pop-up window about the new Super Admin on the next page. Log out and log in again.
---
# 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://knowledgebase.autorabit.com/product-guides/arm/arm-administration/user-management/changing-super-admin-in-arm.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.
