---
title: Super Admin and Account Admin
slug: turbine-user-guide/super-admin-and-account-admin
createdAt: 2026-11-18T08:52:55.738Z
---

**Super Admin** is an account-level privilege that gives access to settings that **Account Admin** does not have. This topic explains how the two differ, which settings need Super Admin, and how to manage Super Admin access safely.

:::hint{type="info"}
Super Admin access is available only to **Turbine Platform (TP)** customers.
:::

## Super Admin and Account Admin

Super Admin is created when Turbine is installed. It is separate from Account Admin. You cannot assign Super Admin from the Turbine UI.

| Role              | Covers                                                                                      |
| ----------------- | ------------------------------------------------------------------------------------------- |
| **Account Admin** | Day-to-day administration: users, roles, groups, tenants, and most **Admin Panel** settings |
| **Super Admin**   | Everything Account Admin covers, plus tenant feature settings and account feature flags     |

## Settings That Require Super Admin

### Tenant Feature Settings

1. Open **Admin Panel**.
2. Go to **Settings > Tenant > Features**.

A Super Admin can turn tenant feature settings on or off, including **Hero AI**.

- With legacy RBAC, the **Features** tab is available to a Super Admin.
- With Enhanced RBAC, the **Features** tab is available to a Super Admin, or to a user whose role has the **Tenant Feature Flags** permission (read and update).

### Account Feature Flags

A Super Admin can change account-level feature flags. The flags that enable Enhanced RBAC are system flags. The **Features** page shows them as read-only, so a Super Admin changes them through the API. After those flags are on, an Account Admin manages roles and groups. An Account Admin cannot change the flags. See [Enable Enhanced RBAC on the Turbine Platform (On-Prem)](https://docs.swimlane.com/turbine-user-guide/enable-enhanced-rbac-on-the-turbine-platform-on-prem).

## Licensing

Super Admin does not override, expand, or change license entitlements or usage limits. A Super Admin can change **Features** and feature-flag settings in the UI. If your license does not allow a capability, turning on a **Features** setting does not make that capability available.

## Check Who Has Super Admin

With legacy RBAC, a visible **Features** tab means the signed-in user is a Super Admin. The **Users** page does not show Super Admin status. To check another user, sign in as that user and look for the **Features** tab.

## Best Practices

- Keep the number of Super Admin users to the minimum required. More than one Super Admin is allowed, including while the install-time Super Admin account still exists.
- Use Account Admin for routine administration. Reserve Super Admin for feature and flag changes, such as Hero AI.
- Treat Super Admin accounts as highly privileged. Use named accounts, and apply the same password and access controls you use for other privileged accounts.
- Change **Features** and other Super Admin settings under change control, in an approved window, and take a backup or snapshot first.
- Record who has Super Admin in each environment. Review that list after a restore or other major change.
