As Admins, the ability to reuse Assets has an impact on budget and resources—helping the team focus more on creativity rather than rebuilding repetitive components.

Assets can be linked across different Projects in Flow Production Tracking. Whether you have a library Project or any other Project, this functionality allows for reusing Assets across Projects.

Contents

• Workflow Overview Video
• Reusing Assets by linking them to Shots
• Reusing Assets by linking them to Parent and Sub Assets
• Turning on cross-Project linking on Detail Pages
• Linking Assets from the Projects Page
• Autocomplete filtering
• Using Connection Entities to track cross-Project Asset linking
• Permissions
• Duplicating and forking Assets
• Integrations and workflows

Workflow Overview Video

Reusing Assets by linking them to Shots

Here are the steps for linking Assets to Shots across Projects:

1. From the source Project that has the original Asset (Project A), navigate to the Assets page.

2. Add the Linked Projects field to the page.

3. In the Linked Projects field, add the Project you would like to link the Asset to (Project B)—the Project must exist and autocomplete. This will make it available to use in the Project you are reusing it in. Tip: you can also bulk update this field.

   

   

   

4. Navigate to the Project's Shot page that you would like to reuse the Asset in (Project B).

   

5. Now that the Assets have been shared from Project A (the source Project) to Project B, you can link these Assets to a Shot using the Assets field on Shots.

   

   

Reusing Assets by linking them to Parent and Sub Assets

Here are the steps for linking Assets across Projects using Parent Asset and Sub Assets:

1. From the source Project that has the original Asset (Project A), navigate to the Asset page.

   

2. Add the Linked Projects field to the page.

   

3. In the Linked Projects field, add the Project you would like to link the Asset to (Project B)—the Project must exist and will autocomplete. This will make it available to use in the Project you are adding it to.

   

   

   

4. Navigate to Project B's Asset page.

   

5. Now that the Asset has been shared from source Project A to Project B, you can link this Asset in the Parent Asset or Sub Asset fields.

   

Turning on cross-Project linking on Detail Pages

To see Assets linked to Shots across Projects, ensure that your detail page filters have this functionality turned on.

1. From a detail page, select Link Assets.

   

2. Select Turn on cross-Project linking.

   

3. This will update the page filter and the standard Project filter will be turned off.

   

4. Project filtering can be turned back on from the Page filter or the Link Assets option.

   

   

Linking Assets from the Projects Page

You can also link Assets from the Projects page with the Assets <-> Linked Projects field. This will allow you to reuse any Assets that are within the source Project.

Autocomplete filtering

Cross-Project Asset linking leverages autocomplete filtering. From the source Project, once you link an Asset to other Projects via the Linked Projects field on the Assets page, that Asset becomes available to link to any of the Projects specified in this field.

The Asset can be added to any entity/multi-entity Asset type field.

Using Connection Entities to track cross-Project Asset linking

You can leverage Asset Shot connection entities to track Assets being shared across Projects.

1. From Site Preferences under Advanced, Enable List Pages for Connection Entity Types and add AssetShotConnection.

   

2. Save this Site Preference.

3. From the Project navigation, select the Other dropdown and Asset Shot Connections.

   

4. From here, you can see which Assets are being reused in Shots.

   

Permissions

In order for a user to see an Asset, they need to be assigned to the source project when the See all Projects option is not enabled.

Duplicating and forking Assets

Reusing Assets creates a simple relationship between the Asset from the Project of origin (Project A) and the Project you are linking the Asset to via Parent or Sub Assets and the Assets field on Shots. If you modify the Asset, you will be going into that source asset and modifying it. In other words, the Asset is not being duplicated.

Duplicating and forking the Asset is supported with integrations, where you can create a new Asset in your current project (Project B) and load Asset data from the Project of origin (Project A).

Integrations and workflows

To learn more about cross-Project Asset linking with integrations, see How do I share assets between projects? on the Developer documentation site.

To learn more about workflows, see Cross Project Workflow on our Developer site.