> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/guides/review-and-client-delivery/deliver-final-files-to-a-client.md).

# Deliver final files to a client

Deliver finals with a branded collection, the right download permissions, and links that expire.

**Outcome:** a branded delivery page with exactly the final files, which the client can download only as you allow, protected by a password and an expiry date. You can see when they opened it.

**Who it's for:** producers and agencies handing over finished work.

**Time:** about 10 minutes per delivery.

## Before you start

* Have the approved finals in Shade. If you're mid-review, see [The client review loop](/guides/review-and-client-delivery/the-client-review-loop.md).
* Have your logo and a background image ready if you want to brand the page.

## Steps

{% stepper %}
{% step %}

### Gather the finals in a collection

Select the final files, right-click, and create a new collection, for example `ACME Spring Campaign: Finals`. Collections group files without moving them, and a file can be in several collections at once. See [Creating Asset Collections](https://academy.shade.inc/sharing-and-collaboration/creating-asset-collections).

{% hint style="info" %}
Delivering a whole folder, like `05_Delivery`? Share the folder with a published link instead. The security options below work the same way.
{% endhint %}
{% endstep %}

{% step %}

### Set what the client can do

Open the collection's details in the right sidebar. Every permission is off by default, so turn on only what the client needs:

* **Download included assets**: on, for a delivery
* **Comment**: usually off for finals
* **View asset details and metadata**: on if they need specs or captions. Choose which fields are visible.
* **View Stack Versions**: off, so the client only sees the final version
  {% endstep %}

{% step %}

### Lock it down

* **Link Expiration**: for example, 30 days
* **Password**: send it separately from the link
* **Watermarking**: usually off for finals. While it's on, downloads are watermarked copies rather than the originals.
  {% endstep %}

{% step %}

### Brand the page

Add your logo, a background image, and an icon. Under layout, choose Grid, List, or Tile, and pick a card size that suits the media.
{% endstep %}

{% step %}

### Turn on the link and send it

Turn on link visibility, copy the link, and send it. Published links have analytics, so you can confirm the client opened the delivery.
{% endstep %}
{% endstepper %}

## Variations

* **Send it automatically:** an automation can generate the collection link and email it when the work is approved. See [Tell a client their files are ready](/guides/automations/tell-a-client-their-files-are-ready.md).
* **Make it your default:** to stop people from creating looser links by hand, set up a **Client** link template in **Settings > Sharing** with your standard expiry and password rule, then turn off **Allow custom links**.
* **Reuse a setup:** right-click an existing collection and choose **Duplicate** to keep its styling and permissions for the next delivery.

## Related guides

* [The client review loop](/guides/review-and-client-delivery/the-client-review-loop.md)
* [Tell a client their files are ready](/guides/automations/tell-a-client-their-files-are-ready.md)
* [Set up an agency workspace](/guides/setup-and-migration/set-up-an-agency-workspace.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 following URL with the `ask` and `goal` query parameters:

```
GET https://academy.shade.inc/guides/review-and-client-delivery/deliver-final-files-to-a-client.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 `build a script that syncs our docs to a CMS` 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.