Brightspot can send you a notification when certain events occur, such as when someone publishes an asset or completes a translation.
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 platform.
Because there are so many different types of 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 for visitors to view.
- Translation—Includes messages about translation jobs, such as when a translation starts, ends, or fails due to an error.
- Workflow—Includes messages triggered when assets transition through a workflow.
Editors create subscriptions to these topics, specifying for each desired delivery methods. For example—
- Harrison creates a subscription for publishing articles to the site brightspot.com via text message.
- Olivia creates a subscription for receiving notifications via email when she is mentioned in a conversation.
- Alma creates a subscription for translation jobs that fail via browser notification.
The following diagram is an example of the relationship between events, topics, and subscriptions.
Brightspot periodically runs a job that delivers the message to the subscribers using the requested delivery method. Brightspot removes a message from the queue after each subscriber received the message or failed to receive the message after a certain number of attempts. The messages stay in the queue until purged by another job.
A subscription’s content filter is a set of criteria Brightspot applies to an event. If the event satisfies the criteria, Brightspot sends a notification. You can have a subscription with multiple content filters as illustrated in the following example.
Referring to the previous example, Brightspot sends notifications when any of the following conditions are true:
- An editor publishes an article or gallery to the site Inspire Confidence.
- An event occurred on an asset you are watching.
- An editor publishes an audio or video to the site Inspire Innovation.
One of the content filters you can select when creating a subscription is Match All. In this case, Brightspot checks that all of the conditions in the content filter are satisfied before sending a notification.
Referring to the previous illustration, Brightspot sends a notification when all of the following are true:
- The editor is watching the asset.
- The asset is published simultaneously to the sites Inspire Confidence and Inspire Innovation.
- The asset is an article.
Some editors may want to receive notifications via text messaging. This section describes integrating Twilio as the text messaging service. Integration for other services is similar.
To integrate a text messaging service:
- Log in to your Twilio console, and select the account from which you want to send text messages. The account's dashboard appears.
- Under Account Info, copy the values for Account SID and Auth Token into a text editor.
- In a text editor, open the Tomcat configuration file
- Add lines similar to the following:
<!-- SMS --> <Environment name="dari/defaultSmsProvider" type="java.lang.String" value="twilio" /> <Environment name="dari/smsProvider/twilio/class" type="java.lang.String" value="notifications.TwilioSmsProvider" /> <Environment name="dari/smsProvider/twilio/accountSid" type="java.lang.String" value="putYourAccountIDHere" /> <Environment name="dari/smsProvider/twilio/authToken" type="java.lang.String" value="putYourAuthTokenHere" /> <Environment name="dari/smsProvider/twilio/defaultFromNumber" type="java.lang.String" value="+12028164833" />
Specifies the default text messaging configuration as
twilio. This configuration appears by default in the Sms Provider Setting Key field in step 8.
Specifies the fully qualified class name implementing the text messaging service.
Value for the account ID that you copied in step 2.
Value for the authentication token that you copied in step 2.
Default from number that appears in the recipient’s text message. This number must be one that the SMS service recognizes as authorized to send text messages.
- Save and close the configuration file.
- Restart the Tomcat server.
- In Brightspot, click > Admin > Sites & Settings > Sites > Global. The Edit Global widget appears.
- Under CMS > Notifications > SMS Settings, do the following:
- In the Default From Phone Number field, enter what appears as the "from" number in text messages.
- In the Sms Provider Setting Key field, keep the default configuration (
twilioas in the above snippet), or enter one of the other configurations.
- Click Save.
Brightspot can send messages to external services, such as a listserv or Slack channel. Editors subscribed to those services receive the corresponding messages.
To send messages to external services:
- Click > Admin > Sites & Settings > Sites > Global.
- Click , and in the search field type
System Notifications. A form appears.
- Under System Notifications, click . A form appears.
Under Delivery Methods, click and select one of the following:
- Email—In the form that appears, enter the email for the messaging service (such as a listserv address), or create a new one.
- Microsoft Teams—In the form that appears, select the team and channel.
- Slack—In the form that appears, select the workspace and channel, or create new ones. Brightspot sends a verification message to the destination.
- Text—In the form that appears, enter the phone number for the messaging service, or create a new one.
Repeat to add additional delivery methods.
- Under Subscriptions, click . A form appears.
- From the Topic list, select one of the available topics.
Using the following resources, complete the subscription for the selected topic:
- Click Save.
Whenever your subscriptions trigger a notification, Brightspot adds the notification to the Notifications widget—in addition to sending the notification through the subscriptions’ delivery methods. You also receive notifications when one of your subscriptions fails to deliver a message, such as when an email server is down.
The counter in the header lists the number of unread notifications you have. After you open the Notifications widget, the counter resets to zero.
To view recent notifications:
- In the header, click . The Notifications widget appears.
- Click the notification. Brightspot opens the corresponding item in a content edit page.