> For the complete documentation index, see [llms.txt](https://kryptopips.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kryptopips.gitbook.io/whitepaper/platform/administrator-dashboard/admin-management.md). # Admin Management Within the Admin Management module, administrators can access a comprehensive list of all current system administrators, including their corresponding access rights. Administrators with "Admins" privileges possess the authority to manage the list of administrators by creating new ones, editing existing profiles, or removing administrators as needed. This functionality provides seamless control and oversight of the administrative team within the system. **Create Admin:** Administrators holding "Admins" privileges have the ability to create new administrator accounts through the "Create Admin" button. By selecting this button, a popup window will appear, allowing the configuration of the new admin account details.

Within the Create Admin popup, you will be prompted to enter the new admin's email address and configure their specific access rights. The access rights options include: * Admins: This permission grants the ability to add new administrators, modify the permissions of existing administrators, and remove administrators. * Filters: With this permission, administrators can create their own filters, as well as edit and delete filters created by other administrators. * Tokens: Administrators with this permission can utilize their MetaMask wallet to send tokens to users selected from the user list. * Wallet Unlink: This permission allows administrators to disconnect user wallets from the platform, which proves useful when users need to link a different wallet to the platform. * Resync: Administrators with this permission can initiate a resynchronization process, re-indexing the blockchain starting from the first significant block for the smart contract. By customizing the access rights for each new admin, the system ensures that administrators have the appropriate privileges for their assigned roles and responsibilities.

After the successful creation of the admin account, you will receive the secure login seed for the new admin. It is crucial to carefully record and securely provide this seed to the designated user. The secure login seed serves as a critical piece of information for accessing the admin account and should be handled with utmost care to ensure the rightful user's authorized access to the system.

**Edit Admin:** Administrators with "Admins" privileges possess the capability to modify pre-existing administrator accounts. By clicking on the permissions list, the administrator can access the "Admin Settings" pop-up. Within this interface, permissions can be added or removed as necessary. Once the desired changes have been made, simply click the "Apply" button to save the modifications.

**Delete Admin:** In order to remove administrators, the administrator performing the action must possess the "Admins" permission. To initiate the deletion process, locate the "Delete" button adjacent to the desired administrator and click on it. Subsequently, a "Remove admin" popup will appear, prompting for confirmation. Click the "Yes" button within the popup to confirm and proceed with deleting the administrator.

--- # 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://kryptopips.gitbook.io/whitepaper/platform/administrator-dashboard/admin-management.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.