Permissions control access to Projects, Collections, folders, and assets. They allow fine control over a user’s access to the functions of DF Studio.
Applying permissions to a container (such as a Project, Collection, or folder) allows administrators to designate which users can view, create, upload, download, share, edit, or write metadata in that location. Permissions may also be assigned globally to the entire DF Studio Library.
Configure User Permissions
Each user has a set of permissions which apply everywhere in the Library where custom permissions have not been defined. These are referred to as “base permissions”, and can be modified from the Settings screen under “Users and Teams”.
Users with “Admin” status control all operations in a DF Studio account, including setting permissions for other users. Access to view and modify account settings or billing information may also be granted on this page.
The Library section defines the user’s base permissions for the DF Studio account Library. (These permissions can be overridden for individual Library items, as described below.) The following roles grant a set of permissions automatically:
- Owner: Allows moving, deleting, and permission management on folders, Projects, Collections, in addition to all function-specific permissions in the list below.
- View Only: Users may view Projects, Project details, metadata, Activity, and Storage. They may collect images in the Bin, and can print contact sheets.
- No Access: Login is allowed, but no visibility of Library assets unless explicitly granted (see Configure Local Library Permissions below).
In addition, it is possible to set the following function-specific permissions:
- Create Projects/Folders: Allows creating new folders and Projects, and uploading files to those Projects.
- Upload: Allows uploading new files.
- Share Collections: Allows creating Collections which can be viewed by others and putting assets into Shared Collections (see below).
- Organize Assets: Allows renaming assets, moving them into Setups within a Project, and changing Storage status (Active / Cold).
- Edit Selects: Allows creating Edits, setting select levels, modifying other users’ shared Edits.
- Write Metadata: Allows modifying details on Projects and metadata on images. Also allows managing Metadata Terms on individual Projects.
- Download: Allows downloading original assets.
- Send: Allows sending Messengers, creating Web Portfolios, and publishing to a remote service.
Enable Asset API access for accounts that require programmatic access outside of the DF Studio user interface. (These accounts are rare; see Enterprise Asset API for more information.)
Users may also be added into Teams, which can be useful in defining specific permissions for individual Library items (described below).
Click “Add Team” from the Users and Teams Settings page to create a new Team and add users.
Configure Local Library Permissions for Individual Items
A user’s base Library permissions apply to all items in the DF Studio account Library, and are inherited by folders, Projects, and Collections within the Library. These permissions may be overridden locally at any level of the folder hierarchy, using the Permissions overlay.
From this screen, permissions may be granted to a user or Team by typing the name into the Assign Permissions field and checking the appropriate boxes below.
Use the row of checkboxes to specify local permissions for the selected user or Team. To remove a user or Team from this local permissions list, click the “remove” icon at the right of that row.
To modify default local permissions for all user accounts not specifically defined above, click the “edit” icon to the right of the inherited permissions displayed under the “Everyone Else” heading.
By default, permissions from containers higher in the Library hierarchy will be inherited, meaning the assigned permissions for any folder, Project, or Collection automatically match the permissions of the folder it resides in. These inherited permissions may be augmented by using the Assign Permissions process described above. (To adjust inherited permissions for a user or team already listed in the Assign Permissions section, click the “edit” icon at the right of the row.) If necessary, inheritance can be turned off by clicking “OFF” beneath “Inherit Permissions”.
This setting only applies to inheriting permissions from folders above the current Library item. By default, permissions granted on this screen will be inherited by any items created below it in the folder hierarchy. To clear all customized permissions settings from any existing items below the current Library item and match their permissions to the current item, check the box next to “Clear Enclosed Permissions” before clicking “Save”.
Control Access to the Permissions Settings
All admin users have the ability to open the Permissions overlay and adjust any of the settings, including the creation or removal of assigned permissions for specific users or teams. Owners of Projects and Collections can also modify these settings in the Permissions overlay for Projects and Collections that they own. To prevent Owners from making these modifications, switch the Locked toggle to “On”.
With the Permissions overlay locked, only admin users are able to change permissions. Individual users can be granted access to unlock the panel using the “Unlock” setting in the Assign Permissions section.
Like all settings in the Permissions overlay, the Lock setting is inherited when “Inherit Permissions” is turned on.
Visual Screen Protection (VSP)
Use the VSP toggle to require the display of the Visual Screen Protection overlay for all users viewing the current library item. The VSP setting is inherited exactly like the other settings configurable in the Permissions overlay.
When VSP is enabled, a new checkbox labeled “VSP Off” appears in the Assign Permissions section. When this box is checked, the specified user or team will see images without the VSP overlay. For more information, see Configure Visual Screen Protection.
Collection Sharing and Local Library Permissions
Collections can be created in three sharing modes: Private, Shared, or Custom. This mode can be modified using the “Permissions” button.
Collections created with custom sharing settings will be able to configure local Library permissions for the Collection, exactly as described above.
Private Collections can only be seen by their creator and admins, and can contain any assets the owner has access to view.
Shared Collections can be seen by any user which can navigate to the location of the Collection. Users are only able to put assets in a Shared Collection if they have 'Share Collections' permission over the assets. Users will have the same access to the assets that they do to the assets in their source Project.