Subscriptions

You use subscriptions to receive notifications for those events—such as when you are mentioned in a conversation—that matter to you. Below are the most common types of subscriptions.

Subscriptions for conversation events

Every time an editor posts to a conversation, Brightspot checks if other editors are mentioned in the post. If so, Brightspot sends notifications to those other editors who have a conversation subscription.

Referring to the previous illustration—

• Sam receives notification via his browser and email when he is mentioned in a conversation.
• Sally receives notification via Slack and her browser when she is mentioned in a conversation.

Subscriptions for publish events

Every time an editor publishes an asset, Brightspot sends corresponding notifications to those editors who are subscribed to the publish event. Because publishing events occur very frequently, you can design your subscription to focus on only those publish events that matter to you.

Referring to the previous illustration—

• Sam has two subscriptions:
  
  • Whenever anyone publishes any content type to any site, he receives a notification via his browser.
  • Whenever anyone publishes an article to any site, he receives a notification via email.
• Sally also has two subscriptions:
  
  • Whenever anyone publishes an image to the site Inspire Confidence, she receives a notification via her browser.
  • Whenever anyone publishes a video to the site Inspire Innovation, she receives a notification via email.

Subscriptions for workflow events

Every time content transitions from one status to another in a workflow, Brightspot sends corresponding notifications to those editors who are subscribed to the workflow event. Because workflow events occur very frequently, you can design your subscription to focus on only those workflow events that matter to you. The following diagram illustrates how granular your workflow subscription rules can be. (The transitions in the diagram are based on the illustration in Create a custom workflow.)

Referring to the previous diagram—

• Sam has two subscriptions:
  
  • When any content for any site transitions through Submit or Resubmit in the Reporter workflow, Sam receives a notification via his browser.
  • When articles for any site transition through Submit or Resubmit in the Reporter workflow, Sam receives a notification via email.
• Sally has two subscriptions:
  
  • When images for the site Inspire Confidence transition through Approve in the Proofreading workflow, Sally receives a notification via her browser.
  • When videos for the site Inspire Confidence transition through Approve in the Proofreading workflow, Sally receives a notification via email.

Subscriptions for translation events

Every time a translation transitions from one status to another (such as from Pending to Complete), Brightspot sends corresponding notifications to those editors who are subscribed to the corresponding event. Because translation events occur very frequently, you can design your subscription to focus on only those events that matter to you. The following diagram illustrates how granular your translation subscription rules can be.

Referring to the previous diagram—

• When Sam submits articles for the site Inspire Confidence to Lingotek, and the translation fails, he receives a notification via email.
• When Sally submits articles for any site to any translation service, and the translation status changes, she receives a notification via her browser.

This section covers setting up your subscriptions in Brightspot.