Collections can be private or shared. Private Collections are visible only to the user who created them and the administrators of the DF Studio account. Shared Collections can be viewed by any user who can navigate to the folder where the Collection is stored. 

Create a Shared Collection

The sharing mode of a Collection is configured when the Collection is created. Create a Collection by moving the mouse pointer over the “+New” button and clicking the “Collection” button.

Select Shared in the New Collection overlay to create a Shared Collection. 

Specify the folder where the Collection should be stored and then click the “Save Collection” button to create the Shared Collection. 

Create a Shared Collection From Selected Assets

To create a Shared Collection from a group of selected assets, navigate to a Project or Collection where the assets are displayed, or gather the assets in the Bin. Select the assets that will be added to the new Collection, and click the “Collection” button in the toolbar at the bottom of the window. (To add all assets in the current view, click the “Collection” button without selecting assets.)

In the Add to Collection overlay, select “New Collection” and then select “Shared”.

Specify the folder where the Collection should be stored and then click the “New and View” button to create the Shared Collection. (Click “New and Stay” to create the Collection but remain in the current view.)

Share a Private Collection

To modify the sharing mode of an existing Collection, click the “Permissions” button from the Collection Inspector.

The Collection Inspector appears when viewing a Collection in the workspace, or when viewing a list of items in the workspace with a Collection selected.

Click “Shared” to update the sharing mode, then click the “Save” button to commit the change.

Shared Collections and Permissions

For DF Studio accounts with node permissions enabled, users are only able to add assets to a Shared Collection if they have been granted the “Share Collections” permission over the assets. Users’ access to assets within the Collection will be determined by their access to those same assets in the Project where the assets are stored.

Accounts with node permissions will also be able to configure custom permissions for a Collection, beyond the private or shared options. For more information, see Control Access With Permissions Settings.