Support and Documentation

Overview of notifications

During the course of a day, thousands of events occur throughout Brightspot. Editors publish assets, comment on assets, complete assignments, edit graphics, and much more. For each event, Brightspot can emit a message, and editors can retrieve those messages over email, text messaging, or other messaging platforms.

Because there are so many different messages, Brightspot organizes them into the following topics:

  • Assignment Desk—Includes messages about new or updated assignments and pitches.

  • Conversation—Includes messages about conversations containing editors' names.

  • Publish—Includes messages about publishing, such as when an asset is pushed to a web server.

  • Translation—Includes messages about translation jobs, such as when a translation starts, ends, or fails due to an error.

  • Workflow—Includes messages about assets transitioning from one status to another in a workflow.

Editors create subscriptions to these topics, specifying for each subscription its desired delivery methods. For example—

  • Harrison creates a subscription for receiving text messages pertaining to articles published to brightspot.com.

  • Olivia creates a subscription for receiving emails when she is mentioned in a conversation.

  • Alma creates a subscription for receiving browser notifications when translation jobs fail.

The following diagram is an example of the relationship between these events, topics, and subscriptions.

Overview of notifications
Figure 40. Overview of notifications


Brightspot periodically runs a job that delivers messages to corresponding subscribers using the requested delivery method. Brightspot stops sending a message after each subscriber received it or after a number of failed attempts. The messages stay in the queue until purged by another job.