> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/run-the-platform/tenants/provide-files-to-tenant.md).

# Providing Files to a Tenant

How to share files from the parent vSAN with a tenant, including ISO images, VM disk images, and other uploaded files.

A service provider can provide files, that are uploaded to the vSAN, to a tenant. For help in the initial upload of files to the parent vSAN, see: [**Uploading Files to the vSAN**](/run-the-platform/storage/uploading-files-to-vsan.md)

## Provide a File to a Tenant

1. From the top menu, navigate to **Tenants** > **List**.
2. **Double-click** on the desired **tenant**.
3. Click **Add File** on the left menu.
4. Select ***File Type*** from the dropdown list (HINT: you can select --ALL-- to get a listing of all files available, regardless of type; this will include \*.raw files(VM disk images) from the parent VDC.)
5. **Select a file** from the dropdown list.
6. Click **Submit** (bottom of page).

The process is near-instant as it is done with a branch command. The file is now available to the tenant within their own [**Files**](/run-the-platform/storage/uploading-files-to-vsan.md) section.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verge.io/run-the-platform/tenants/provide-files-to-tenant.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.