Admin Panel

The Admin Panel in NocoDB gives organization-level oversight and control. Administrators use it to:

• monitor usage metrics
• manage workspaces and projects
• provision and track users
• configure Single Sign-On (SSO)
• update branding settings

This guide describes each section of the Admin Panel. Use these sections to maintain governance, enforce security, and keep user and workspace configurations aligned with the standards of your organization.

Navigation Overview

Users with administrative privileges can open the Admin Panel. In the bottom-left corner of NocoDB, open the user menu. Click Admin Panel.

Dashboard sits on its own at the top of the sidebar. The sections below it are grouped under these headers:

The badges mark what a section needs beyond the base license: a plan name for a section that plan unlocks, Add-on for one sold separately. The Security group is hidden only for an unlicensed deployment whose users have turned off upgrade prompts.

To go back to the main NocoDB application, click the Back button in the top-left corner.

Dashboard

The Dashboard gives a high-level overview of key metrics across your NocoDB deployment. It is a basic control center where admins monitor system usage and see the scale of the data and the number of users in their organization. The current functionality is limited, but the visual summaries show a few critical numbers at a glance.

Displayed Metrics:

To see what a metric counts, hover over its info icon. For example, Users counts every account in the deployment, including accounts that are not in a workspace. Thus this number can be higher than the number of members in User Management.

Workspaces

The Workspaces section lists all active workspaces in your organization. Each workspace shows its name, the number of members, and the number of projects. Admins use this view to monitor workspace-level participation and data volume.

Actions:

Projects

The Projects section shows all databases in the organization, from all workspaces. Each project shows its name, its workspace, and the number of members. Admins use this central view to monitor project creation and ownership.

Actions:

User Management

The User Management section lists all users in the organization. Each member shows an Org Role (Org-Admin, Org-Creator, or Org-Viewer) and the date the member joined. The Org Admin manages organization membership, assigns org-level roles, and provisions workspace access.

The list header shows the total number of members and the number of billable Editor seats. A member uses a paid seat when the member has an Editor or higher role at the workspace level, in any project, or on any interface.

Changing Org Roles:

To change the org role of a member, click the role dropdown next to the member. The roles are:

The role of the Org Admin shows as a different badge. For details on org role constraints, see Organization-level Roles.

Actions menu:

Click the Actions (three dots) menu next to a member. The menu has these options:

To add new users to the organization, click the + Invite User button.

For more details about organization-level roles, see Organization-level Roles.

Teams

In the Teams section, Org Admins create and manage organization-level teams. Workspace teams belong to one workspace. Org teams are available in all workspaces of the organization, and you can give them roles in any workspace or project.

The teams list shows the name, badge, number of members, and creator of each team, and an actions menu. Teams with sub-teams have an expand/collapse toggle. To change between tree view and flat view, use the toggle buttons in the toolbar.

To create a new team, click the + New Team button. To make the new team a sub-team, select a parent team. This is optional.

Click the Actions (three dots) menu next to a team. The menu has these options:

For detailed team management instructions, see Organization Teams.

Single Sign-On (SSO)

In the Single Sign-On (SSO) section, organizations configure central authentication for their users. With SSO, admins manage fewer individual credentials, and user authentication follows the enterprise security policies.

For detailed setup instructions, refer to the SSO documentation.

Environments

The Environments section defines the environments that every workspace in the organization shares, for example Production and Staging. Each integration keeps separate credentials and settings per environment, so a project connected to a staging database in one environment reaches the production database in another.

An environment has a name, a description and a color, and one environment is marked as the default.

AI Skills (Enterprise)

The AI Skills section holds the skills available to NocoAI across every workspace in the organization. Install a skill from the catalog, or author one here, and it is then offered in every workspace instead of being set up project by project.

SCIM

In the SCIM section, Org Admins configure SCIM v2.0 provisioning. SCIM manages users and groups automatically from an identity provider (IdP). When SCIM is enabled, NocoDB syncs user onboarding, offboarding, and group membership changes from your IdP automatically.

In this section, you can:

• Enable or disable SCIM provisioning
• Configure the default org role for provisioned users
• Copy the SCIM endpoint URL and provisioning token for IdP configuration
• Regenerate the provisioning token if it is compromised
• Remove the SCIM configuration completely

For detailed setup instructions, refer to the SCIM Provisioning documentation.

Audit (Scale)

The Audit section shows the audit trail for the whole organization, rather than for one workspace. The columns, filters and detail panel are the same as the workspace audit. Refer to Workspace Audit for what each event records and how to filter the list.

Setup (self-hosted only)

The Setup section configures the two services the deployment needs beyond the database: Email, for invitations, password resets and record emails, and Storage, for attachments. Each one lists the supported providers; click Configure to enter the credentials, or Edit to change them.

Until both are configured, an orange icon shows next to Setup in the sidebar. The equivalent settings can also be supplied as environment variables.

White Label (Add-on)

The White Label section replaces the NocoDB name, logo and colors with your own across the application and the sign-in page. It is a paid add-on on self-hosted Scale and above. Refer to White Labelling.

License (self-hosted only)

The License section is available in self-hosted deployments. Super admins use it to activate a license key. The license key unlocks features such as SSO, audit logs, and advanced access controls.

1. Paste your license key into the input field.
2. Click Save. The status banner turns green, and NocoDB enables paid features immediately.

To purchase a license, see Purchase a License. For the complete activation guide, including airgapped and offline modes, see License Activation.

Settings

The Settings section holds two instance-wide options:

The two options are linked. When you turn on Restrict workspace creation to super admin only, NocoDB turns on Allow signup only using invite url as well and greys it out, because a user who signs up without a workspace has nowhere to go.

Additional Notes

• Only users with the Org Admin role can open the Admin Panel. Org Creators and Org Viewers do not have access.
• Actions in the Admin Panel apply at the organization level. They affect all workspaces and projects.
• All changes in this panel apply immediately and globally across your NocoDB deployment.