Data Admin overview
The role that owns and governs the Lakehouse.
A Data Admin owns the Lakehouse: the managed Apache Iceberg storage where Tenant analytics data lives. You provision and maintain it, structure its namespaces and tables, and govern who can read and write its data. The underlying role is the Tenant's Data Admin role.
Data Admin vs Tenant Admin
Keep the boundary clear. A Tenant Admin runs the Tenant: its Compute, data-source connections, users, and grants. A Data Admin runs the Lakehouse: its namespaces, schemas, tables, views, and the access to that data. The two overlap at provisioning (creating the Lakehouse resource may be done by the Operator, the Tenant Admin, or you), but its ongoing structure and data governance are yours. If the question is "how is the Lakehouse data organized and who can query it," it is a Data Admin concern.
The Data Admin role owns the Lakehouse, and can also manage access on any resource in the Tenant, not only ones it created, the same Tenant-wide Can Manage Access reach a Tenant Admin has. That authority lets it self-grant Can Use and Can Edit on any Tenant resource, including Compute and Depots it did not create; those self-grants are audited like any other. See Roles & Permissions.
What you cannot do
Manage Tenant settings, invite users, or assign roles: That is the Tenant Admin's job, not yours.
Create domains, or release quarantined Resources: Both are reserved for the Tenant Admin.
Use Compute, Depots, or Secrets by default: You can self-grant
Can Use/Can Editvia yourCan Manage Accessauthority (above), but you don't hold them automatically. Every grant, including to yourself, is audited.
What you run and maintain
Manage the Lakehouse: provision it, then create and maintain namespaces, schemas, tables, and views.
Access control on Lakehouse data: govern who can read and write, including masking and row-level controls.
Monitoring: watch Lakehouse health and usage.
Start with Manage the Lakehouse.
Last updated
Was this helpful?