> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/operate/v1/data-developer/access-and-readiness.md).

# Get access

Before you deploy, three things must be true: you have the access to build, the Tenant has the resources to run what you build, and you have the access to use those resources. Sorting this out first saves a failed deploy later.

## Get the access you need

You hold the `Data Developer` role, which lets you create your own resources, but deny-by-default means you start with no access to shared resources. Request a `Can Use` grant from your [Tenant Admin](/operate/v1/tenant-admin/governance.md) for each one you need:

* The **Compute** your models and pipelines run on.
* The **Depots** (data sources) you read from and write to.
* Any **Secret** your Data Product workload references directly.
* The **Lakehouse** Depot, if your product reads or writes Lakehouse tables.

If your product must run under a service identity rather than yours, ask the tenant admin to set up the **Application User** and grant you `Can Use ApiKey` so you can set `runAsUser`. See the [RunAsUser permissions](/operate/v1/access-model/runasuser-permissions.md).

## What you can already see, without a grant

Separate from the `Can Use` grants above, the Data Developer role also includes tenant-wide discovery access by default, no request needed:

* **Search and explore Data Products**: use the Data Product Hub's search and browse features.
* **Tenant apps access**: sign in and use the Tenant's UI applications (the Hub and other consumption apps), the same baseline a Data Consumer gets.
* **Resource tabs (Metis-powered)**: view the metadata, lineage, and schema tabs Metis surfaces on resources across the Tenant, not just ones you created.

This is visibility only. Finding a product in the Hub, or viewing a resource's metadata tab, does not grant `Can Use` or `Can Edit` on it. You still need an explicit grant to consume a product or act on a resource. The same discovery-vs-consume split applies to a Data Consumer; see [Get access](/operate/v1/data-consumer/get-access.md) in the Consumer section.

## Confirm the tenant is ready

Check that the environment can actually run your product before you deploy. The readiness checklist:

* [ ] **Compute** you can use is attached and active.
* [ ] The **engine Stack** your product targets (for example Vulcan) is installed and healthy.
* [ ] **Depots and Secrets** for every source and destination your product touches exist and are active, and you hold `Can Use`.
* [ ] A **Git repository** holds your project, with a git-sync Secret so DataOS can pull it.
* [ ] If you write to a **Lakehouse**, it is provisioned and you can write to the target namespace.

You can confirm a resource exists and you can use it with `dataos-ctl resource get`. If something is missing, it is a request to your [Tenant Admin](/operate/v1/tenant-admin/tenant-admin.md) (Compute, data sources, grants) or [Data Admin](/operate/v1/data-admin/data-admin.md) (Lakehouse), not something you provision yourself.

For installing the toolchain and the build prerequisites, see [Prerequisites](https://v2.dataos.info/build/get-started/prerequisites) in the Build guide. Once you are ready, the build itself is covered in [Productize](https://v2.dataos.info/build/productize), and shipping it is [Deploy and promote](/operate/v1/data-developer/deploy-and-promote.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/operate/v1/data-developer/access-and-readiness.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.