# Content Hub Setup

{% 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 %}

## Netflix Content Hub & Vendor Submission <a href="#h_01hekks0nsajz0txvbtbnc28mv" id="h_01hekks0nsajz0txvbtbnc28mv"></a>

Netflix's Content Hub is a file hosting and transport service which leverages Aspera for file transfer and Content Hub's web UI for authentication. In order to configure your Netflix project to use Content Hub, please follow the steps below.

## Vendor Submission Setup <a href="#h_01hekkxjpttqdz5yf06a4d0avj" id="h_01hekkxjpttqdz5yf06a4d0avj"></a>

There is no setup necessary for Vendors to use Content Hub with the \[RE]DESIGN Vendor Submission tool, but \[RE]DESIGN must pre-configure a few settings on the backend before the project can leverage it. First, please notify \[RE]DESIGN of the intention to use Content Hub so we can enable it in the Vendor Submission app.

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

## Configuration Setup <a href="#h_01hekkx96p9yk94qa9qkg2yvh9" id="h_01hekkx96p9yk94qa9qkg2yvh9"></a>

The below data are required for \[RE]DESIGN to set up the integration properly:

### Send Content Hub Project ID to \[RE]DESIGN <a href="#h_01hekm1b32s22w67271c77qbng" id="h_01hekm1b32s22w67271c77qbng"></a>

First, sign into Content Hub and choose the project which will be used for the integration.

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

When you click on the project, the Project ID will be shown in the URL. The easiest way to send it to us is to email the entire URL to your \[RE]DESIGN support ticket like this:&#x20;

```
https://contenthub.netflixstudios.com/projects/92311f0-5bd7-11e9-b8ed-0e4d342d506/assets
```

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

### Shared Folder Setup <a href="#h_01hekm8zdpm4s95cxp3k4x59y9" id="h_01hekm8zdpm4s95cxp3k4x59y9"></a>

Every vendor should have their own Shared Folder created by the administrator of the project.

We do not require any specific naming convention, but the vendor folder must be unique to the project - no other shared folder can contain the same folder name. If you are using our Aspera Files integration at the same time, you should use the **same** name for each vendor folder in both applications.

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

### Sharing the Folder <a href="#h_01hekmaxw7qn8k1dnb966vvtnr" id="h_01hekmaxw7qn8k1dnb966vvtnr"></a>

Use Content Hub's folder sharing tools to share the same folder with all users which require access to the same vendor folder. For instance, if you are sharing **vendor\_RVC** with Dennis and Scott at RVC then share with both <dserras@vendor.ext> and <sfritzshall@vendor.ext>.

If you know when the show will be or sure be completed, you can put in an expiration date.

We ask that in preparation you create a shared folder for \[RE]DESIGN to test with. Please share this folder with our test account. In addition, share all the vendor folders with your \[RE]DESIGN integration lead for support purposes.

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

### Adding the Folder in ShotGrid <a href="#h_01hekmgp71yy3gnhzt05dfw58d" id="h_01hekmgp71yy3gnhzt05dfw58d"></a>

The folder for each Vendor should be added to ShotGrid on the People > Groups page, in the Remote Vendor Folder field. Note that this is also used by the Aspera Files configuration, so if you are using both integrations, you should use the same shared folder names in both Aspera and Content Hub.

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

## Vendor Authentication <a href="#h_01hekmjwfbxjees572wmbpnfqj" id="h_01hekmjwfbxjees572wmbpnfqj"></a>

When the vendor attempts to upload a submission with the [Upload Submission](/artist-anywhere/vendor-workflows/upload-submission.md) tool, Content Hub will load in the web browser and request the user to sign in. This authentication will last for 36 hours before it requires the user to sign in again. Once the vendor has signed in, the upload will begin.

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

## Production Authentication <a href="#h_01hekmp5n5th1b9vpr6t64ah9c" id="h_01hekmp5n5th1b9vpr6t64ah9c"></a>

Currently the Content Hub authentication **cannot be extended past 36 hours**. Therefore we recommend the production to re-authenticate every morning to keep Content Hub deliveries ingesting. To do so, click on the Gear icon in the [Ingest Queue](/artist-anywhere/i-o-tools/ingest-queue.md).

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

The default Transfer Setting which appears should be the Content Hub setup. If not, please choose Content Hub.

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

Click the Reset Credentials button in order to force Content Hub to re-authenticate and allow you to sign in again.&#x20;


---

# 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/additional-documentation/content-hub-setup.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.