You have the ability to customize the branding of the system between divisions and/or brands using multiple branded site skins. Separate skins allow one Widen Collective site to have different URLs, colors, or themes that match the needs of different brands, divisions, or companies. The data on both sites is the same because sites are connected to the same master database of information. Users can be allowed to access any skin site, with access to assets and metadata controlled by asset groups, user roles, and permissions. It's important to note that when you have multiple branded sites, you (unlike general users) may be interacting with metadata structures, categories, tasks, and filenaming rules across divisions or product brands.

For example, for skin site A:
  • The URL is
  • The background is blue
  • The logo is BRAND A
For skin site B:
  • The URL is
  • The background is green
  • The logo is BRAND B

Consider the following for skinned sites:
  • You will have access to all metadata types and categories on skinned sites; however, metadata types and categories cannot have associated roles and permissions, because these areas of the site must be included or not included.
  • The name of the site is seen by all users in email notifications and other areas of the site. A generic name that applies to all users should be used.
  • Order approvals can be routed to sub-level managers or asset admins, and admins will receive order approval notifications.
  • Multiple metadata types should be used to segregate separate metadata fields.
  • Separate category structures should be created for each skinned site to avoid having categories that need to be segregated.

Multiple branded site guidelines

Global configurations

These configuration points within your Collective site are global and not based on a user's role. If selected, they will be automatically enabled for the site:

  • Document text search
  • EULA displaying when users log in, on the Pickup page, or on collection share pages
  • The embedded IPTC, XMP, and Exif metadata fields mapped to metadata fields in the Collective
  • Whether or not IPTC and Exif metadata displays on the Asset Details page
  • Exporting metadata with orders, including whether or not a metadata file is included on the Pickup page
  • Sharing assets with multiple recipients
  • Spotlight searches
  • Favorite assets (who can favorite is role based, but the feature is either on or off)
  • Commenting on assets (who can comment is role based, but the feature is either on or off)
  • Rating assets (who can rate is role based, but the feature is either on or off)
  • Watermarking assets
  • Metadata field values displaying on thumbnail images
  • Branded video training on the account page (unless it's included in Dashboard system messages)


These permissions give administrative privilege independent of the asset group associated with that role:

  • Administrate Metadata Types
  • Administrate System Messages
  • Administrate Asset Categories
  • Administrate Asset Upload Profiles
  • Administrate Deleted Assets
  • Administrate Asset Conversion Formats
  • Export Asset Search Reports
  • Export Order Reports
  • Export User Reports
  • Export Upload Reports
  • Access Insights


If applicable privileges are assigned to an administrative role, you can select user- and asset-related administrative task alerts and email notifications from your user profile. Some administrative task notifications are global settings. Depending on the task, you may receive user- or asset-related task notifications that can be filtered or ignored.


If files are uploaded with the same filenamethe upload profile setting will determine whether they are placed in a conflicted state or automatically made the current version of an existing asset with the same name.

If the uploader does not have permission to interact with the earlier uploaded file because it is in an asset group they do not have access to, the uploader will only be able to rename or delete the uploaded file.