Brightspot CMS User Guide

Overview of a DAM environment

In a typical DAM scenario, you make assets available through a dedicated site, such as Subscribers log in to the site and select the assets they want to use.

  • If the assets require approval before use, Brightspot sends a request to the appropriate editor.
  • If the assets do not require approval before use, the subscriber can immediately download or share them.

The following illustration describes a typical DAM workflow.

DAM workflow

Implementing this workflow requires setting up a new site and managing subscribers through the Users Integration.

See also:

Previous Topic
Digital asset management
Next Topic
Configuring DAM
Was this topic helpful?
Thanks for your feedback.
The elements that get you up and running in a matter of days, from pre-built content types, to modules, to landing pages.

Content types
Landing pages
Everything you need to manage and administer content within Brightspot CMS, including plug-and-play integrations.

Admin configurations
A guide for installing, supporting and administering code on the Brightspot platform, including integrations requiring developer support to use.

Field types
Content modeling
Rich-text elements