Warning! This documentation is outdated. Visit help center for the latest documentation.

Configuring storage scenario

A storage scenario can be configured to instruct ftrack on how your files should be stored and tracked. Read more about storage scenarios and why you should use them here.

../_images/settings_configure_storage_scenario.png

The active storage scenario can be configued from System Settings ‣ Media Management ‣ storage scenario. To configure a storage scenario you will need to have ftrack connect running.

If you’ve already configured a storage scenario you will see the name of the currently active scenario.

Note

You can also see the JSON parameters of the scenario, for advanced users and developers this may be good for debugging purposes.

If you haven’t already configured a scenario or want to update an existing scenario you can press Configure Storage Scenario. From here you will be able to select from a list of storage scenarios.

By default ftrack comes with a Centralised storage scenario.

Note

You need to download and log into ftrack Connect before configuring a storage scenario.

Centralized storage scenario

The centralized storage scenario is suitable for studios with one central storage where published files are stored. To start using it, simply select Centralised storage scenario from the drop-down and click Next. Follow the steps presented to you in the wizard.

At the end you will be asked to confirm your configuration before saving it. Please take a moment to read through and verify the information that you have filled in.

Congratulations! You’ve now configured a storage scenario. Make sure to restart ftrack connect and any other applications that communicates with ftrack. This is neccessary in order for the new storage scenario to become available.

Note

The storage that you intend to save your files on must be mounted and available on all computers that need to publish and import data.

Troubleshooting

I cannot see anything in the Select storage scenario dropdown:Make sure that you have ftrack connect started and that you are properly logged in with a API key.