Admin Console
The Admin Console is available at /admin and provides platform-wide management capabilities for self-hosted Entropy Data installations.
Only Super Admins can access the Admin Console. Regular users and organization owners do not have access. Super Admins are configured via the APPLICATION_SUPERADMINS environment variable.
The Admin Console is organized into the following sections, in the order of its navigation:
- Dashboard: platform overview with key statistics like total organizations, users, active users, and data products, plus a Version card showing the running build version, its release date, and a link to the changelog.
- Organizations: view, edit, and delete organizations. Configure name, vanity URL, logo, branding, SSO, and custom scripts.
- Users: search, filter, edit, and delete user accounts. Reset passwords or revert SSO users to password login.
- Active Users: real-time view of currently active users and their last activity.
- SSO: every single sign-on setup of the installation and the organizations that log in through it.
- SCIM: the organizations that provision users or groups through SCIM, with their groups, provisioned users, and group mapping.
- Data Governance Checks: monitor and manage automated policy check runs.
- Search AI: review AI-powered search conversations across all organizations.
- Intelligence: audit all LLM/AI interactions, including token usage, duration, and tools used.
- Notifications: send every notification type to a webhook to check a Slack, Microsoft Teams, or Google Chat endpoint.
- Emails: the log of every email the installation sent, failed to send, or skipped.
- Ingestions: view and cancel data ingestions (asset imports) across all organizations.
- Integrations: the writing integrations of all organizations, which write metadata such as descriptions back to a data platform.
- Uploaded Images: every image uploaded in any organization, to spot abuse or content issues.
- Metrics: view system-wide platform metrics for monitoring health and usage.
- Diagnostics: run health checks: database ping, external IP address lookup, and test email delivery.
All sections are read-only unless stated otherwise.
SSO
One row per SSO setup, identified by issuer and tenant. A shared client registration such as azuresso serves many Microsoft Entra tenants, and each tenant gets its own row. Each row shows:
| Column | Description |
|---|---|
| Issuer | The OAuth2 client registration id the organizations log in through, and its login URL /oauth2/authorization/<issuer>. |
| SSO Host | The hostnames of the organizations behind this setup. |
| Tenant | The identity provider tenant, if the organizations name one. |
| Client Registration | The client ID and provider URI of the registration this installation was started with, or Not configured when no registration with this id exists. Nobody can log in through a setup marked Not configured. |
| Orgs, Organizations | The organizations that log in through this setup, with their member count and an Auto Join badge when anyone who logs in through this SSO joins the organization automatically. |
| Users | Distinct users across these organizations: a user who belongs to two of them counts once. |
Client registrations that no organization uses are listed as well, marked Unused. Comparing both halves shows misconfigurations: an organization pointing at a registration the installation does not have, and a registration nobody points at. To set up SSO, see SSO.
SCIM
Lists every organization with a SCIM footprint: it synced groups, has a group mapping configured, or has users that SCIM created. The table shows the number of Groups, their distinct Members, the Provisioned Users, whether a Mapping is configured and when it changed, and the Last Group Change. The list is sorted by the last group change, most recent first.
Open an organization to see its details:
- SCIM Groups: display name, external ID, member count, and when and by whom each group was last updated. Raw payload shows the JSON the identity provider sent with the last
POSTorPUTof the group. Membership changes sent asPATCH, which most identity providers use, do not refresh it, so it can be older than the membership shown. - Provisioned Users: the accounts SCIM created in this organization, with email, name, status (Active or Deactivated), join date, and last login. Users who already existed when SCIM adopted them carry no SCIM origin and are not listed.
- Group Mapping: the YAML that maps SCIM groups to roles and teams, with who last updated it and when. Without a mapping, groups are synced but grant no roles or teams.
SCIM keeps no sync log. Last Group Change only moves when a group actually changed, so a connector that ran with nothing to sync leaves no trace, and an organization whose sync stopped keeps its old timestamp.
To set up SCIM, see SCIM.
Notifications
Sends a test message of every notification type to a webhook URL, to check that an endpoint accepts and renders them. Pick the channel type (Slack Webhook, MS Teams Webhook (Workflows), MS Teams Webhook (O365 Connector), or Google Chat Webhook) and enter the endpoint URL. The messages use example data from a made-up organization and do not create a notification channel. For Google Chat, the messages are sent one second apart because of its rate limits.
To set up notification channels for an organization, see Set up Notifications.
Emails
The email protocol records every attempt to send an email, with one of three statuses: Sent, Failed, or Skipped (not sent because the organization switched that email off; the reason reads disabled-by-organization). Use it to answer questions like "did this user get the invitation?".
- Filters: organization, recipient (contains), email type, status, and a date range. Columns can be sorted.
- Volume: a chart of emails per hour over the last 24 hours, and totals for the last 24 hours, 7 days, and 30 days, split by status. The volume follows the filters except the date range.
- Details: open an entry to see organization, type, mail provider, sender, recipient, CC, BCC, subject, language, status with its reason, and the body.
Secrets are removed from a body before it is stored: one-time tokens in verification, password reset, invitation, and stop-watching links are masked as ***.
The protocol is configured with environment variables:
| Environment Variable | Default | Description |
|---|---|---|
APPLICATION_MAIL_PROTOCOL_ENABLED | true | Set to false to switch the protocol off; then nothing is recorded. |
APPLICATION_MAIL_PROTOCOL_STORE_BODY | true | Set to false to keep only the envelope (addresses, subject, status) and drop the body. |
APPLICATION_MAIL_PROTOCOL_RETENTION_DAYS | 90 | Entries older than this are no longer listed and are deleted. |
Integrations
Lists the integrations of all organizations that write metadata to a data platform, for example data contract descriptions written as comments to Snowflake, Unity Catalog, AWS Glue, or PostgreSQL. Asset imports are not listed here; they are on the Ingestions page.
The totals at the top count the integrations and their tables in sync, unresolved, and failed, the events waiting in the queues, and the failing tasks. Each row shows the integration and its platform, the organization, its Tables (in sync, unresolved, failed, nothing to write), its Queue, and its Task, including how many times in a row the task failed and when it last ran. Integrations that need attention come first: a failing task, then failed tables, then unresolved tables.
Uploaded Images
Lists every image uploaded in any organization, newest first, such as the logo of an organization or the icon of a team, a data product, or a user, with a summary of the number of images and their total size. Each row shows a preview, the organization, the image type, its size, who uploaded it, and when. Click a thumbnail to open the full image.