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

Tenant readiness

The end-to-end sequence that makes a Tenant ready to use, and which role owns each step.

Getting a Tenant ready is a shared responsibility. No single role does everything: the Operator provisions and hands over the Tenant, the Tenant Admin sets up access and data sources, and the Data Admin provisions the Lakehouse. This page is the end-to-end view: the steps that take a Tenant from "created" to "a team can build and run on it," and who owns each one.

Use it to coordinate a hand-off, to see where your part fits, or to check nothing is missing before a team starts work.

Who does what

The steps run roughly in order, grouped by the role that performs them. Each links to the canonical how-to.

Operator

The Operator does the setup that requires Instance-level authority, then invites a Tenant Admin and steps back to Instance-level Manage access and Monitoring.

1

Provision the Data Plane in your cloud. See Provision Data Plane.

2

Create the Tenant in Instance Admin. See Create Tenant.

3

Attach the Data Plane and at least one Compute. See Attach the Data Plane and Compute.

4

Deploy the required Stacks: the MCP Server and its OAuth broker. See Deploy Stacks.

5

Invite the Tenant Admin and assign the role. See Assign the Tenant Admin.

Tenant Admin

The Tenant Admin takes over the running Tenant, and these steps can begin as soon as the role is assigned. A Tenant is usable on day one once at least one data source and the required Stacks are ready.

1

Register data source Secrets and Depots. The Operator may seed the first data source during setup, but registering and governing data sources is the Tenant Admin's ongoing job. See Add data sources and Secrets.

2

**Invite the rest of the team and grant Can Use on shared resources to users or Roles. See Manage access.

Data Admin

The Data Admin provisions and owns the Lakehouse (its namespaces, schemas, tables, and views) separately from the resources the Tenant Admin governs, and only when a team requires one.

1

Provision the Lakehouse, if the team needs one. See Manage the Lakehouse.

For role definitions and the capability matrix behind these assignments, see Roles & Permissions.

Readiness checklist

A Tenant is ready to hand to a team when:

Once the Tenant is ready, a Data Developer builds the Data Product on Vulcan, together with the data-product-supporting resources it needs, such as Nilus. See the Data Product Developer overview.

Last updated

Was this helpful?