Skip to main content
Use the Super Admin dashboard to manage all organizations and users on your OpenHands Enterprise installation from one place. A Super Admin is an instance-wide administrator. This role is separate from the organization roles Owner, Admin, and Member.

Open the Dashboard

Choose Super Admin from your user menu, or Super Admin Dashboard from the organization selector. Only Super Admins see these entries. The first user to sign in to a new installation is a Super Admin. When an existing installation is upgraded and has no Super Admin, the user who signed in first becomes one. To make more people Super Admins, see Manage Super Admins.

First-Install Setup

On a new installation, the first Super Admin goes through a setup wizard after signing in:
  1. Add your license key or offline license file. You can skip this step and add the license later.
  2. Enter your company name and logo.
  3. Name your first organization. You become its owner.
After the wizard, add an LLM for the organization, then continue with the setup guide. The wizard and setup guide appear only for that first user. An installation that already has users when it is upgraded does not show the wizard to anyone.

Setup Guide

The setup guide tracks the remaining steps to get the first organization running agents:
  1. Add an LLM.
  2. Connect Git.
  3. Create an automation.
  4. Add an integration (an MCP server).
  5. Invite users.
Open the guide from Setup guide in the Super Admin navigation or from the lower-right corner of the app. Each step is marked done when OpenHands detects it. To hide the guide, remove it from the navigation. To show it again, turn on Show Setup guide in Instance Settings. For Connect Git, take the GitHub MCP tour, which starts on the GitHub card in the MCP library and opens the install dialog, or use the built-in OAuth app through Auth Providers and Settings > Integrations. For GitHub App webhook events, see GitHub Event Automations.

Review Usage

Use the Dashboard page to review usage across organizations. It has Overview, Users, Models, and Conversations tabs.
  • Choose All organizations, or compare selected organizations.
  • Choose a time window: 7 days, 30 days, 90 days, or year to date.
  • On the Conversations tab, search and filter conversations, export them as CSV, or stop a running conversation.

Manage Organizations

The Organizations page lists every organization with its member count, contact email, and status.
  • Create an organization: Click Create organization. Enter a name, contact name, and contact email, and choose the owner. You are the owner unless you choose another user.
  • Open an organization: Click its name, or choose View organization from the row menu. The Super Admin role does not make you a member. To open an organization you don’t belong to, grant yourself access and choose a role.
  • Invite people: Choose Invite by email from the row menu, enter email addresses, and choose a role. This option requires email delivery, such as SMTP.
  • Remove an organization: Choose Remove from the row menu. You can’t undo this. OpenHands refuses to remove an organization when a member has no other organization.
Personal workspaces belong to their users. You can’t open, invite people to, or remove another user’s personal workspace. For settings that control personal workspaces and a default organization, see Configuring Organizations.

Manage Users

The Users page lists every user with their organizations, roles, and status. Pending invitations appear in the list too. Click a user, or choose Manage user from the row menu, to change their access:
  • Organization access: Add the user to an organization with a role, change their role, or suspend, resume, or remove their membership in the organizations you select.
  • Suspend account: Block the user from signing in and using API keys in every organization. Click Activate account to restore access.
  • Delete user: Remove the user’s account, API keys, and conversations in every organization. You can’t undo this.
OpenHands refuses to remove, demote, or delete the last owner of an organization, and to suspend or delete the last Super Admin. You can’t suspend or delete your own account.

Manage Super Admins

Super Admins can create organizations, invite users, and manage other Super Admins.
  • Grant: On the Users page, choose Grant Super Admin from the user’s row menu and confirm.
  • Revoke: On the Super Admins page, choose Revoke from the row menu and confirm. You can’t revoke your own access. Ask another Super Admin to do it.

Instance Settings

Use the Instance Settings page for settings that apply to every organization:
  • Company logo: Replaces the OpenHands logo in the top left.
  • Company name: Appears at the top of the Settings navigation.
  • Allow users to have personal workspace: Shows whether personal workspaces are on. Change it in your deployment configuration. See Configuring Organizations.
  • Show Setup guide: Shows or hides the setup guide. Only the first Super Admin can change it.
  • Enable Service Accounts (beta): Lets organizations run automations under a service account instead of a personal account.

License

Only Super Admins can manage the license for an OpenHands Enterprise installation. Get a license key or an offline license file from Customer Center. To add or change the license:
  1. Open Settings.
  2. Click your name in the lower left, then click Super Admin Dashboard.
  3. Click License in the navigation.
  4. Enter your license key, or upload your offline license file.
A license set in your installation’s configuration takes precedence and can’t be changed on this page. On a new installation, the setup wizard also asks for the license key or offline license file.

Super Admin Access

The first user to sign in to OpenHands Enterprise is the installation’s Super Admin. To make specific users Super Admins, open the Admin Console configuration and enter their email addresses in Experimental > Super Admin Emails. Those users become Super Admins on the next upgrade. Use this setting to recover or guarantee Super Admin access without database access. The field is empty by default, which turns the setting off. Setting it doesn’t change access for users who aren’t listed.