Admin governance
Admin provides temporary governance while a new Aragon account is being set up. Its Admin plugin lets admins configure the account and install its ongoing governance immediately, without waiting for a vote. Removing Admin completes the handover to that governance.
Starting with Admin
Account creation installs Admin with the connected wallet as the initial admin. An admin can add other admins, configure the account, and install governance without waiting for a vote. Each action creates and executes a proposal in one transaction, preserving the account's common proposal history and presentation.
Admin is provided for this bootstrap. The governance designer does not offer it as a new governance choice, and the current self-service flow cannot reinstall it after removal.
A freshly created account still needs its intended ongoing governance installed, and installing plugins requires permissions on the DAO. Installing Admin during creation supplies that authority immediately.
Onboarding dashboard
When Admin is the account's only visible governance process, its dashboard guides the transition into governance. An admin can use the governance designer where available or work with Aragon on a custom setup. Other visitors see that the account is still being set up and can inspect its admins.
Admin controls
Admins can share setup responsibility by changing the admin list. Each admin can act immediately, so changing that list changes who can exercise the authority.
Account settings shows the installed Admin plugin and its members. Manage admins lets an existing admin add or remove members. The change executes in one transaction, with a proposal retained in the account's history. At least one admin must remain in this form; ending admin control uses plugin removal instead.
Handing over governance
The admin installs the chosen governance through the designer's prepare-and-apply flow. Admin executes the installation proposal immediately.
Installing governance does not by itself end admin control. Removing the Admin plugin completes the handover once the replacement is ready.
Removal boundary
Remove all admins uninstalls the Admin plugin. This ends the bootstrap: the former admins lose the authority that plugin gave them, and the account depends on its remaining governance.
For the normal Admin setup, the app requires another process with unrestricted execution on the same account before starting removal. A process on a linked account does not satisfy this requirement. If replacement governance is missing, the app directs the admin to create it.
Before preparing removal, a critical confirmation asks the admin to consider that handover. Its purpose is to make the loss of admin authority explicit and establish that the remaining governance is sufficient. Removal is then prepared and submitted as a proposal through the selected governance process; the proposal must execute for Admin to be removed.
An admin can submit its own removal through Admin. The removal executes immediately in that transaction, without a token-holder vote.
Last updated on