Notifications

Brand Atlas notifies in two places: the in-portal Inbox and email. The Inbox is the canonical record; email is a convenience to ensure you do not have to live in the portal to know what is happening.

​

What the Inbox contains

The Inbox is in the sidebar. It holds:

• Update Requests waiting for review (brand owner).
• Comments on sections you are subscribed to.
• Mentions of you in a comment or request.
• Guest Pass activity (created, expired, accessed).
• Tier and billing events (renewal, failed payment, scheduled downgrade).
• AI events. Oswald drafts ready for review (Guardian). Henry usage milestones (Keeper+).

The Inbox is filtered by category. Each item can be marked read, snoozed for a specified period, or acted on inline.

​

Email notifications

By default, brand owners receive email for:

• Update Requests raised.
• Failed payment and renewal events.
• Authorship transfer requests.
• Scheduled downgrade reminders.
• Status page incidents affecting the atlas.

Team members receive email for:

• Responses to Update Requests they raised.
• Mentions of them in comments.
• Welcome and password reset.

Editors receive everything a team member receives, plus notifications for sections they have edit rights on.

​

Configuring notifications

Open Settings → Notifications to adjust which events trigger email. Three controls:

• Per-category toggles. Switch off email for any category. The Inbox continues to record the event.
• Daily digest mode. Bundle non-urgent notifications into one daily email. Urgent events (failed payment, security) still send immediately.
• Snooze. Pause all email for a defined period. The Inbox continues to record.

Settings are per-user, not per-atlas. Each team member configures their own.

​

What is not configurable

Three categories of email are always sent and cannot be switched off:

• Security events. Sign-in from a new device, password change, two-factor authentication change.
• Billing failures. Failed payment after the third retry. Required for the grace period to work.
• Account closures. Cancellation confirmation, account deletion, authorship transfer completion.

These are operationally important and override notification preferences.

​

Slack and Microsoft Teams

Brand Atlas can post notifications to a Slack channel or Microsoft Teams channel via incoming webhook. Open Settings → Integrations to configure. The integration sends a subset of the Inbox (new Update Requests, mentions, milestone publications) to the channel. The integration is one-way: the channel receives notifications but does not let the team act on them; actions still happen in the portal.

​

Notification timing

Notifications are sent in real time for urgent events and batched within five minutes for non-urgent events. Email arrives in the order events occurred. The Inbox is updated immediately. The atlas does not send notifications during scheduled maintenance windows; events accumulate and are released when the maintenance window ends.

​

Related pages