Be told what happens in the tenant management console

The console started writing everything down last week, but the record was somewhere you had to go and look. A partner found out that a workspace they are responsible for had been suspended by opening the console and reading the activity page. Now the console tells you instead.

A bell in the header, on every page. It carries the number of things that have happened since you last looked, and no badge at all when there is nothing new. Opening it previews the newest few, with a way to read them all or clear the lot.

A notifications page lists everything in full, newest first, in the same words the activity record uses — who did it, what they did, which workspace it was done to, and when. Each one takes you to the workspace it concerns.

Seven things are worth telling you about: a workspace being created, suspended, reactivated, deleted, recovered or permanently removed, and somebody’s role in a workspace being changed. Not everything the console records is a notification — inviting a user, assigning a partner and granting console access are all still on the activity page without interrupting anybody.

You are told about the workspaces you are responsible for. The Sustentus team sees the whole estate. A partner sees the workspaces currently assigned to them and nothing else, including when the page is opened directly rather than followed from the bell. If a workspace moves between partners, its notifications move with it.

You are never notified of your own actions. Suspending a workspace yourself does not raise a badge for you — only for everybody else who can see it.

Read and unread are yours alone. Marking one read, or marking everything read, changes nothing for anybody else. Marking read does not remove anything either: the notification stays, shown as read, and the activity record behind it is untouched.

Nobody is emailed about any of this. This tells you when you are in the console; being told when you are not is coming separately.