Notifications

cmssy notifies you in the app, and by email where the message deserves to leave the app. There are six kinds, and they split into two groups.

Someone did something

• You were mentioned in a comment.
• Someone replied to your comment - unless you wrote the reply yourself, or were already mentioned in it.
• A task was assigned to you.
• A task's status changed.

These carry enough context to land you in the right place: the page, the block, and the comment or task itself. Opening one takes you to that comment on that page, not to the top of the page to hunt for it.

Something needs attention

Two are not social, and are the ones to actually act on.

Usage warning. Fired when an organisation crosses 75% of its monthly API requests or bandwidth, and again at 100%. Each level fires once per period rather than on every request past the line - the point is a warning, not a siren. This is the notification that arrives before your site starts answering 429 rather than after.

Webhook disabled. A webhook endpoint that keeps failing gets turned off, and you are told. Without this, the failure mode is silent: your site simply stops revalidating and nobody notices until the content on it is a week old.

Reading them

The inbox shows unread first with a count, and you can mark one or all as read. Read state is per person - marking your own copy read does not silence a colleague's.

Next steps

• Comments and tasks - where four of the six come from.
• Plans, limits and usage - what the 75% is measured against.
• Webhooks - why an endpoint gets disabled, and how to bring it back.