Skip to content

Notifications and what reaches you

Reading your notifications, choosing the categories you hear about, and the plain fact that nothing reaches you while Social Studio is closed.

Updated

Notifications tell you when something needs you: an approval, a comment mentioning you, being added to a workspace, a connection that needs attention.

They are in-app only. Nothing is emailed, because there is no mail layer in this product. Nothing is pushed to your phone either: device tokens genuinely register, and there is no delivery worker on the server and no notifier in the app, so nothing arrives while Social Studio is closed. No setting turns that on.

Everything is kept on the server and is waiting the moment you open the app. The practical advice the mobile app itself gives is the right one: check in rather than waiting to be told.

BEFORE YOU START

  • Active membership of the organisation. There is no separate permission; notifications are yours.
  • Nothing to configure. Categories are opt-out, not opt-in.

STEPS

  1. Open Notifications, or go to /app/notifications for your organisation.
  2. Read the unread count and the list.
  3. Choose "Mark read" on an item, or "Mark all read" for the lot.
  4. Look at "Notify me about" underneath. A ticked box means you hear about that category.
  5. Untick a category you do not want. It is silenced for you only; everyone else still hears about it.

WHAT YOU SHOULD SEE

The unread count falling as you read, and the preference saving as soon as you change it.

WHAT THIS WILL NOT DO

  • It will not email you.
  • It will not reach your phone while the app is closed.
  • It will not notify anyone when a task is assigned. Task assignment writes no notification.
  • It will not honour quiet hours. The setting exists behind the API and nothing reads it, so it is not offered in either client.
  • It will not let you mark one item read on your phone. The mobile screen offers "Mark all read" only, and no category preferences.

WORTH KNOWING

Six categories are offered: approval, comment, assignment, publish, connection and system. Five of them are actually emitted. Nothing in the product currently writes a publish notification, so unticking that category silences something you were never going to hear.

IF IT DOES NOT WORK

  • "You're all caught up." means nothing is unread.
  • "That preference could not be saved." means the change did not take. The page puts the tick back where it was.
  • "Those notifications could not be marked as read." and "That notification could not be marked as read." are the two failures.
  • On mobile, "Nothing has been missed - notifications are kept on the server and will all be here when you reconnect." appears when you are offline. Take it literally.
  • On mobile, "Too many requests just now - these are still unread. Try again shortly." means the rate limit, not a failure to read them.
  • "That device token is already registered to a different account." means the phone was signed in as somebody else. Sign out there first.

COMMON QUESTIONS

Why register a device token at all if nothing is sent?

Because registration is the half that works, and it keeps working. When a delivery worker exists, the tokens are already there. The app is explicit that the remaining work is engineering on both sides.

Can an administrator turn notifications on for me?

No. Muting is per person and per category, and nobody else's setting affects yours.

  • Securing your account

    Turning on two-factor authentication, keeping recovery codes, ending browser sessions and revoking credentials, and what the step-up check is for.

  • Reviewing and deciding on content

    Working the approvals queue, what "edited since submitted" means for your decision, and the separation-of-duties rule that stops an author approving their own work.

  • Commenting on work

    Leaving threaded comments on a note, a content item or a task, mentioning teammates, and the difference between an internal comment and one a client can read.