Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Tenant Admin overview

The role that runs a Tenant day to day: resources, access, governance, and health.

A Tenant Admin runs a Tenant day to day. After an Operator creates the Tenant and hands it over, the Tenant Admin becomes responsible for making the Tenant usable for teams: setting up resources, managing access, and watching Tenant-level health.

Tenant Admin vs Data Admin

Both are senior Tenant roles, but their responsibilities are different:

  • Tenant Admin has administrative control over the Tenant's resources and users. If the task is who can use this Compute or data source, or who belongs to this Tenant, it is the Tenant Admin's responsibility.

  • Data Admin has control over the Lakehouse, including its namespaces, schemas, tables, views, and data governance. If the task is how Lakehouse data is structured or governed, it is the Data Admin's responsibility.

Your authority

Your authority is the Tenant boundary, and it is broad within it. You can:

  • Invite users and assign Tenant roles.

  • Create resources such as Compute, Secrets, and Depots.

  • Grant or revoke access on any resource in the Tenant, including ones you did not create (useful when a creator leaves or is unavailable).

What you do not get by default is silent access to Compute, Depots, Minerva, or Secrets; like everyone else you self-grant Can Use, and that grant is audited. The Access control explains why.

What you cannot do

  • Act outside your Tenant: Creating or deleting Tenants, attaching the Data Plane, or managing Instance-level setup is the Operator's job. Your authority stops at the Tenant boundary.

  • Export data from DataOS applications, or manage metadata directly: Both belong to the Data Admin, not to you. Being the highest-privileged Tenant role does not mean you automatically inherit every capability the other roles hold.

Day-to-day responsibilities

Your work falls into four recurring tasks, each with its own runbook:

  • Create compute: provision the node pools Data Product workloads run on.

  • Add data sources and secrets: connect the Tenant to external systems with Secrets and Depots.

  • Manage access: onboard users, grant developers Can Use on Compute and data sources, and set up the ApplicationUser and runAsUser mechanics.

  • Monitoring: watch the Tenant's Compute and resource health, and how to check it.

A good first pass after a Tenant is handed to you:

  1. Confirm the Compute and data sources you were given.

  2. Invite the rest of the team and assign roles.

  3. Grant developers or the Roles they belong to the Can Use permissions they need to start building.

Start with Create compute, or jump straight to Manage access if the resources are already in place and you are onboarding people.

Last updated

Was this helpful?