Beaulieu manages a large volume of digital assets across multiple brands, business units, regions, markets and customer types.

As part of our DAM strategy, we are evaluating Optimizely DAM as a replacement for our current Wedia DAM. However, one of the key capabilities preventing us from migrating is the lack of a flexible permission model based on both asset metadata and user attributes.

To successfully support our governance model, we require a permission framework where access is determined dynamically by matching asset metadata (tags) with user attributes (roles, groups and tags). This approach enables scalable governance, minimizes manual administration and ensures that users only have access to the assets relevant to their role and responsibilities.

Our current Wedia DAM supports this type of governance, allowing permissions to be automatically evaluated based on asset metadata and user profiles. This has proven essential for efficiently managing a large, enterprise-scale DAM with multiple brands, regions and customer segments.

We would like Optimizely DAM to offer similar functionality through a flexible Attribute-Based Access Control model to enable organizations like ours to migrate without compromising governance, security or operational efficiency.

Requested functionality

We would like Optimizely DAM to support Attribute-Based Access Control, where permissions are determined by evaluating both asset metadata and user attributes.

Rather than assigning permissions to folders or individual assets, access should be automatically evaluated using configurable rules.

Asset Metadata

Assets can contain metadata such as:

Branding
Asset name
File title
Asset type
language
Department
Topic
Disclaimer
Room type
ALT tags
Binary information (asset nature, orientation, width, height, etc.)

Usage rights: external/internal / expiration date / authorized channel / Unauthorized regions

PIM Sync information (if the asset is sent to PIM, information from PIM is sent to DAM)
send to PIM (yes/no) / PIM external keys) / Product group / Product family / Collection / Sub-collection / Offered in countries / Design / Colour group / Colour tone / Colour code) / Article code etc.

User Attributes:
- Branding
- Product family
- Product group
- Collection
- Sub-collection
- Asset branding
- Asset type
- Language
- Department
- Topic
- External vs. Internal communication
- Offered in countries
- Communication tool
- Authorized channels
- Unauthorized channels
- Status (public use / internal use / draft / archived)

Example:
Customer of BerryAlloc selling laminate in Norway => he will only be able to see the assets of BerryAlloc related to laminate that are sold in Norway (not collections exclusive in France). He will not see the assets in French of Flemish but only in Norwegian + English)

Sales person of Beauflor => he will be able to see all assets of Beauflor including internal assets and archived assets but will not be able to see assets in draft.

Dynamic groups:
If an asset is added - it will automatically be added to all channels as this is based on tags. Idem is an asset is archived - it won't be seen anymore by the user
We have actually over 200 different dynamic groups

PIM Integration:

Data from DAM is sent to the PIM (if we click on field "sent to PIM). In the PIM the asset is enriched with data and part of this data is sent to DAM.