Skip to main content
Documentation & User Guides | FotoWare

Using metadata to control access to assets in a FotoWare archive

FotoWare archives have access lists to allow a manager to define the level of access users and groups have in each archive. These users and groups can be imported from an identity provider such as Active Directory, Azure AD or any SAML-compliant provider.

At times, it may be desirable to give certain users access to only a subset of files within an archive. This can of course be done with albums, but as albums are static containers, they will have to be manually updated by someone to reflect new content.

A better option is to use metadata "flags" within the archive in combination with automatic search filters that are applied at the access list level

Example - Approving content for general use

Let's assume that files are uploaded to a FotoWare archive where they are reviewed by a single manager or a group of managers. Before an asset is released and made available by regular users, they have to be approved for general use.

DAM Editors can see all the content in an archive and have markers to identify assets that have not yet been approved. They may "release" assets to regular users of the system (Dam Users) by means of an approval procedure; i.e. selecting the assets executing an "release" action in FotoWare. Once an asset is approved, regular users will be able to see and use the approved assets in the archive

How to set it up

On the archive's access list, entries are added for DAM Editors and DAM Users.

Our objective is to make DAM Users see only content that has been approved, or released, so as illustrated in the screenshot below, the DAM Users group has a search filter specifying that member of that group will only see the assets in the archive where field 811 contains the tag Released.

clipboard_e14b7aa165933df4d1a8716b38b288a39.png

 

Next, you will have to make an action whereby the DAM Editors can release assets:

Make a new Extended action and set it to modify the source assets by executing a macro that changes the value of field 811 to Released:

clipboard_e89bd1767f6f5869594b881e85f870f84.png

Next, make sure only DAM Editors have access to use the action:

clipboard_e9da594428586ae2d0b8df26b6cc19299.png

 

Now you've successfully created the mechanism that is used to limit the assets that regular users can see to released assets only.

Next, you may want to create markers that DAM Editors can use to tell which assets have been released and which haven't:

The screenshot below shows the setup of a marker that shows on assets that have been released to users: It shows only if field 811 equals Released.

Similarly you can create the reverse marker that displays on assets that have not been released. (Set the Match Type to Does not equal)

clipboard_e89989a26af10c0f252dcd3cf82a8c8eb.png

Result

DAM Managers can now select assets and release them to regular users of the system. Also, managers can easily tell from the visual markers on each asset whether it has been released to users or not.

clipboard_eea783cb27a808008624997f9355ac8e0.png

  • Was this article helpful?