Brightspot CMS User Guide

Overview of a DAM environment


In a typical DAM scenario, you make assets available through a dedicated site, such as assets.mydomain.com. 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 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.
Our robust, flexible Design System provides hundreds of pre-built components you can use to build the presentation layer of your dreams.

Asset types
Module types
Page types
Brightspot is packaged with content types that get you up and running in a matter of days, including assets, modules and landing pages.

Content types
Modules
Landing pages
Everything you need to know when creating, managing, and administering content within Brightspot CMS.

Dashboards
Publishing
Workflows
Admin configurations
A guide for installing, supporting, extending, modifying and administering code on the Brightspot platform.

Field types
Content modeling
Rich-text elements
Images
A guide to configuring Brightspot's library of integrations, including pre-built options and developer-configured extensions.

Google Analytics
Shopify
Apple News