# Make Delivery

{% hint style="warning" %}
Please be aware that some information in this article may be inaccurate or out of date as we work to update it to be in line with our tools' latest functionality. Thank you for your patience as we update our documentation portal.
{% endhint %}

The Make Delivery application is a tool designed to generate Deliveries from inside the ShotGrid web interface. This tool utilizes Published Files, which are linked to a specific Version, to locate the source files and proceed with the tool. To launch, ensure SG Desktop is running. Then, select "Versions" or "Playlists" in the ShotGrid site, right-click, and choose "Make Delivery" from the Applications section.

{% hint style="info" %}
This application is plugin-based, so your configuration may contain a different list of functions than those below.
{% endhint %}

## Launching Make Delivery tool <a href="#launching-make-delivery-tool" id="launching-make-delivery-tool"></a>

To start the application, please do one of the following:

Select a group of Versions on a Version List page, right-click, and choose "Make Delivery"

<figure><img src="/files/zz85P1i2JxglmXfR0iq9" alt=""><figcaption></figcaption></figure>

From a Version's Detail page, go to the action menu in the top right corner and choose "Make Delivery"

<figure><img src="/files/S5bLQeYGIFAvWE9xoQTk" alt=""><figcaption></figcaption></figure>

From a Playlist page, select one or more Playlists, right-click, and choose "Make Delivery"

<figure><img src="/files/iqYAtDQdytRMxaRGoe1E" alt=""><figcaption></figcaption></figure>

From a Playlist detail page, go to the action menu in the top right corner, and choose "Make Delivery"

<figure><img src="/files/zfgn0Tzn4FIgmOD0756v" alt=""><figcaption></figcaption></figure>

## Using the Make Delivery tool <a href="#h_01herj0zt3mg2bmtxkf99047kx" id="h_01herj0zt3mg2bmtxkf99047kx"></a>

<figure><img src="/files/RLvMlf9aAjPwF7WerqRH" alt=""><figcaption></figcaption></figure>

The Make Delivery interface consists of two sections: the file list (on the right side) and the actions (on the left side).

### Selecting Files <a href="#selecting-files" id="selecting-files"></a>

At the top of the Actions section is a list of all publish formats which will be acted upon - select and deselect from that list to limit the files checked on the right side. Similarly, on the right side, select and deselect groups of files or individual files with the checkboxes.

### Copy Published Files plugin <a href="#h_01herj69xgj26mmf6kt7sydayy" id="h_01herj69xgj26mmf6kt7sydayy"></a>

This tool allows the user to copy files linked in SG to a local path, either on the server, to a second disk, or over a VPN. It will create a Delivery in SG as a record of the transfer.

Choose the delivery template setup for the paths, set the location you wish the files to be copied, set the Delivery Name, and decide whether to include an RV session file.

<figure><img src="/files/oJcOkEamJDTiY7QdV0Ok" alt=""><figcaption></figcaption></figure>

### Create Delivery plugin (Artist Anywhere only) <a href="#h_01herj8axjmtnxe30qxrhtfj7w" id="h_01herj8axjmtnxe30qxrhtfj7w"></a>

The Create Delivery tool will build a new Delivery to Vendor inside of SG and send it to the vendor via Cyclone.

Set the Delivery Template which will be used for the received files, select the Group who should receive the files (they must be set up with an AA Bucket).

If you check the **Create RV Session File** checkbox, the selected group will receive **rv\_session.rv** as part of the Delivery. &#x20;

<div align="left"><figure><img src="/files/1jhjUTg9EgQfvUJEiqaS" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions: 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:

```
GET https://artist-anywhere.gitbook.io/artist-anywhere/i-o-tools/make-delivery.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.