How moderators get notified

• Why no per-event pushes

  A push for every report would mean five or six interruptions a day on a quiet week and dozens on a busy one. Every moderator is a real person doing this around a day job, family time, or their own studio's bookings. So InkMap pushes you when there's a useful signal to push on, not because something happened.

  What that looks like in practice:

  • Reports and confirmations don't push. Even if a card lands in your queue right now, your phone won't buzz.
  • In-app counters update in real time. Open the Community Standing tab on your profile, tap into the Moderation Tab, and the queue counts reflect what's actually pending. Same on the admin web panel for moderation admins and admins.
  • Moderation Admins and platform admins get a single daily digest. One push a day at 9 AM UTC summarising what's in your queue. No work pending? No push.
  • Rejection disputes are the one carve-out for senior mods. When a collector files a dispute against a content-check rejection (a tagged practitioner or community moderator rejected the post during initial review), the assigned senior moderator gets a push — these disputes are low-volume and time-sensitive, and the assignee is the only person who can act, so suppressing this push would mean disputes sit unseen. Disputes filed against post removals after an upheld report route to an admin, not a senior mod (see How moderation works for the rejection-vs-removal distinction). Senior mods don't get a push for removal disputes because they aren't the assignee.

  The model has one explicit escape hatch: a per-account override in your push preferences (covered below) that turns the per-event pushes back on if you really want them.

• Regular and senior moderators

  If you're a Community Moderator (10+ moderation trust) or a Senior Moderator (35+), your default notification model is in-app only for the day-to-day flow.

  • No push on assignment. A card landing in your queue doesn't ring your phone.
  • No push on confirmations. Senior-tier confirmation requests don't push either — the Path A "@user_x recommends removing this post" card shows up silently in your queue.
  • An in-app row lands in your bell-icon feed every time a card is assigned to you, so the feed itself is your "you have new work" signal. The row deep-links to the Moderation Tab.
  • The counters on the Moderation Tab are the source of truth. Open the tab and you see exactly what's pending in each queue: assigned cards, confirmations, disputes, collection-review posts. No round-trip required.

  One exception for Senior Moderators: incoming rejection disputes still push. When a collector files a dispute against a content-check rejection and the system assigns it to you specifically, you receive a "Post Under Review" push so the dispute doesn't sit unseen for days. This sits outside the trimmed-down model on purpose — these disputes are time-sensitive (the collector is waiting), volumes are low, and the assigned reviewer is the only person who can act on it (it's not a queue you'd notice by glancing at counters). If you'd rather not get even this one push, you can override it from the type-level toggles in your push preferences. Disputes filed against post removals (after an upheld report) route to admins, not to you, so the push above only fires for rejection disputes.

  This means you control when you do most moderation work. The platform makes it easy to find when you're ready; it only buzzes you when something genuinely needs your specific attention.

• Moderation Admins and platform admins

  Moderation Admins (granted out-of-band — see Community roles & trust) and platform admins get the daily digest.

  • One push per UTC day, fired at 9 AM UTC. The body lists the buckets that have pending work: e.g. "You have 3 reports, 2 disputes to review."
  • Buckets with zero items are omitted from the body. The push only mentions what actually needs your attention.
  • If your queue is empty at 9 AM UTC, no push fires at all. Silent days are silent.
  • The push only fires once per day. Even if the cron is triggered twice (rare; only happens in dev), the second run is a no-op.
  • The in-app counters and the in-app row mirror the digest. A tappable "Moderation Digest" row appears in your bell-icon feed the same morning the push fires, so you can revisit the summary later in the day.
  • Escalations are surfaced specifically. When the regular chain can't close a report — for example, when the reported post belongs to a Moderation Admin or the senior-confirmation deadline expired — the Reports tab shows a banner at the top counting how many of your active reports are flagged as escalated, so you know which ones need extra attention.

• How to opt out

  If even one push a day is too much, you can turn the digest off without losing the in-app surface:

  • Open your push notification preferences and toggle Moderation Digest off.
  • The in-app counters and the bell-icon feed still update in real time — you just stop receiving the morning push.
  • The toggle is reversible at any time. Turn it back on and the next morning's digest fires as usual.

  If you want the opposite behaviour — per-event pushes for every report assignment or senior confirmation, the way it used to work — you can flip the matching toggles in type-level overrides inside the same push-preferences screen. The role-based defaults send nothing; the overrides bring the noise back if that's what you want.

• Edge cases

  A handful of less-common situations worth knowing about:

  • You're a senior mod and also an admin. Admin role wins. You receive the daily digest at 9 AM UTC; you do not receive per-event pushes for confirmation requests as a senior mod, because the admin gate fires first in the role-resolution chain.
  • You're a regular mod assigned to a card but you also explicitly enabled the per-event push. You'll get both the in-app row and the push. Type-level overrides win over the role defaults.
  • You change device or sign in on a new one. The next morning's digest fires to every active device you're signed in on; there's no per-device subscription to manage.
  • Push is critical-priority. The daily digest bypasses your usual quiet-hours window — admins have opted into moderation work by being admins, and 9 AM UTC is already business-hour-ish across Europe. If you set per-account quiet hours, they will not silence the digest. If you want it silent, use the toggle described above.
  • A new role just kicked in. If you crossed the Community Moderator threshold today, the in-app counters start populating the next time a card is assigned. There's no retro-active push.

Frequently asked questions

I'm a senior moderator. Why didn't I get a push when a Path A confirmation landed in my queue?

The senior-tier confirmation push is off by default — that's the whole point of the redesigned model. Open the Moderation Tab and your queue counts include the new card. If you want a push, you can flip it on in your push-preferences screen via type-level overrides.

I'm a senior moderator and I just got a "Post Under Review" push. I thought senior mods don't get pushes?

Rejection disputes are the one exception. When a collector files a dispute against a content-check rejection (the validation card "Reject" outcome), the system assigns it to a specific senior moderator (usually you) for fresh-eyes review — there's no broader queue surface for these disputes, so a push is the only way to make sure it doesn't sit unseen. Disputes filed against post removals after an upheld report route to an admin instead, so a senior mod won't see that flavour of dispute push at all. If you'd rather not get this one either, flip the matching toggle off in your type-level push preferences. The "How to opt out" section above walks through the same screen.

I'm an admin. The daily digest didn't fire this morning.

Two possibilities. First: your queue was empty at 9 AM UTC and the cron silently skipped you — open the Moderation Tab to confirm there's nothing pending. Second: you have Moderation Digest toggled off. Re-check your push preferences.

I'm a community manager about to be granted Moderation Admin. Will I start getting pushes immediately?

Yes — the next 9 AM UTC after you're promoted, the digest will fire for you if your queue has any pending work. Until then, the in-app counters on the Moderation Tab show you what's waiting; you don't need to wait for the push to start clearing it.

I'm not a moderator. Should anything in this article affect me?

No. This article is for moderators. Regular users — collectors, practitioners, studios — receive notifications for content they're personally involved in (validations, follows, comments, etc.) on the normal in-app + push model, completely separate from the moderation regime. See How moderation works for the user-facing report flow.

Can I get a digest at a time other than 9 AM UTC?

Not yet. The fixed UTC time keeps the model simple and predictable; per-account timezone scheduling is a possible future change.

Are these notifications regulated by my quiet-hours window?

Per-event moderation pushes are gated off by default for every role, so quiet hours don't normally matter. The daily digest is marked critical-priority and bypasses quiet hours specifically — if you don't want the morning ping at all, use the Moderation Digest toggle described above.