Browser Notifications

Modified on Mon, 12 Aug at 3:52 PM

Many of us are in and out of different applications and browser tabs all day. For some, Divvy's standard notifications features suffice as dashboard and email notifications keep you in the know. But for those who want real-time alerts as things are happening on your content projects, we've added browser/push notifications that can be activated via your browser settings.

 

The Divvy Details

Users who have browser notifications enabled will be notified in Chrome, Edge, or Safari when:

  • You're assigned to new content items, tasks, and campaigns
  • Comments are added to any of your content items, tasks, or campaigns
  • A task is completed and you're next up in a workflow
  • and MORE!

If you haven't yet enabled browser notifications and would like to, here are guides for activating them in Chrome (shown below), Microsoft Edge, or Apple Safari.


When you first log into DivvyHQ, your browser will automatically ask you if you wish to receive browser notifications. If you decide not to receive them out of the gate, you can easily update this permission later by clicking the padlock icon in the browser url field, and allow DivvyHQ permission to send you browser notifications.




To help make your life a little bit easier, when you click a DivvyHQ browser notification, it will open a new browser tab and take you directly to the associated content item or campaign.


Troubleshooting

If, after enabling the browser notifications, you still aren't receiving the notifications, check your notification preferences within your operating system (Windows, Apple, etc.). Apple settings shown below.



You may find that additional settings need to be configured to display the alerts or play a sound when the alerts fire (if desired).

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article