The Admin Panel is the central control hub for self-hosted Baserow instances. It allows instance administrators to monitor server health, manage users and workspaces, and configure global settings from a single interface.
This guide covers Baserow’s Admin Tools interface for self-hosted instances, including dashboard metrics, health checks, user management, and system settings.
The Baserow Admin Panel gives instance administrators complete visibility and control over their self-hosted environment, regardless of license plan.
Admin Tools is the centralized management interface for self-hosted Baserow instances, giving Instance Admins control over users, workspaces, authentication, system health, and licensing without needing to access the server command line.
It is available on all self-hosted Baserow installations. Admin Tools provides visibility into instance usage, system status, and administrative controls. Only Instance Admins can access Admin Tools; regular users don’t see this option in their interface.
From this panel, Instance Admins can:
While the Admin Panel is available to all self-hosted instances, specific tabs within the panel (such as instance-wide Audit Logs or Authentication) may be locked depending on your active license plan.

To access the Admin Panel, you must be an Instance Admin with “Staff” privileges. This is typically the account created during the initial installation of Baserow.
The sidebar is organized into three logical sections: General, People, and Licenses.
Who is an Instance Admin? The first user who signs up on a self-hosted Baserow instance automatically becomes an Instance Admin with “staff” privileges. Additional Instance Admins can be designated through the Admin Tools interface.
Learn now to make someone an Instance Admin
Learn more: Purchase and install licenses
Upon opening the Admin Panel, the first page is the Dashboard. This provides a high-level snapshot of your instance’s usage and activity.
The dashboard displays real-time counters to help you track adoption:
| Metric Category | Data Points |
|---|---|
| Totals | Total users, Total workspaces, Total applications |
| New Users | Sign-ups in the last 24 hours, 7 days, and 30 days |
| Active Users | Active sessions in the last 24 hours, 7 days, and 30 days |
The Health page offers critical insights into the technical status of your installation. It runs automated checks to ensure your services are communicating correctly.
The page displays the status (Pass/Fail) of the following components:
The Health page also includes manual triggers to verify system responsiveness:
Only users with Staff (Instance Admin) privileges on a self-hosted instance can access the panel. Workspace Admins do not have access to these server-level settings.
Yes. The Admin Panel interface is available to all self-hosted versions (Baserow Open Source). However, specific features inside the panel, such as instance-wide Audit Logs or Authentication, require a license.
If a check like Redis or Celery fails, it usually indicates a service is down or misconfigured in your Docker or server environment. Check your server logs for connectivity errors between the Baserow container and the failing service.
Instance Admins have access to Admin Tools; Workspace Admins do not.
No. Admin Tools is exclusively for self-hosted installations. Cloud users on Baserow.io manage their workspaces through standard workspace settings; they don’t have access to instance-level administration.
This is because you don’t have Instance Admin (“staff”) privileges. Contact the person who originally set up your self-hosted Baserow instance. The first user who signs up is automatically an Instance Admin.
This is because of infrastructure issues with service (database, Redis, storage, etc.). Note which specific check is failing, review logs for that service, verify the service is running and accessible, and check network connectivity between Baserow and the service. Restart affected services if needed
This is because the email configuration is incorrect or the SMTP server is unreachable.
Verify SMTP settings in Baserow environment variables, check SMTP server credentials and connectivity, review firewall rules for SMTP port (usually 587 or 465), and test SMTP connection outside of Baserow. Check email logs for error messages
Admin Tools features:
Authentication and security:
Plans and licensing:
Self-hosted setup:
Still need help? If you’re looking for something else, please feel free to make recommendations or ask us questions—we’re ready to assist you.
Contact support for questions about Baserow or help with your account