Brightspot CMS User Guide

Digital asset management

With Digital Asset Management (DAM), you can stand up a site of proprietary assets that subscribers can browse and use in their own publications. A typical DAM workflow is as follows:

  1. A subscriber submits requests to use your assets.
  2. You approve or deny the requests, and optionally assign an expiration date for the approved requests.

For example, a subscriber requests permission to use an image of your maple syrup in an article. You can grant the request, and subsequently notify that subscriber that the image is no longer usable after January 1, because the product is being discontinued.

Previous Topic
Injecting ads into a listicle
Next Topic
Overview of a DAM environment
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
Landing pages
Everything you need to know when creating, managing, and administering content within Brightspot CMS.

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

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

Google Analytics
Apple News