← All help topics

Notifications

A feed of important events: problems with model requests and good news. The menu shows an unread-count badge.

1What shows up here

Two kinds of events show up in the feed:

  • ⛔ Model request errors — token limit reached, provider unavailable, a failed response. With brief details so you can see the cause.
  • ✅ Positive events — such as successful post publishing.

2No suitable post for the plan

If the plan needed a post today, sources were polled, but no fresh material matched the topic — you'll get a notification. What to do next:

  • 📝 There are unapproved drafts — approve them in «План и очередь постов».
  • ⏱️ Or enable the plan's «Auto-posting» option so suitable posts publish without manual approval.
  • 🔍 No drafts — check «Источники» and «Marketing context» (the sources may currently produce nothing on your topic).

3Service update overview

When the service is updated, a 🎉 notification arrives in the feed with a brief overview of new cabinet features — what's new and where to find it.

  • ✨ One per update: once read, it won't repeat.
  • 🗓️ This way you won't miss useful additions even if you visit rarely.

4No spam: a repeat counter

Repeated events don't create a new record each time:

  • 🔁 An existing unread notification gets a growing counter (×N) and an updated time.
  • ✅ Once you mark it read, the next such event creates a new notification.

5Read state and the badge

Managing the read state:

  • ✅ Mark each notification read, or «Mark all as read».
  • 🔴 The badge next to the «Уведомления» menu item shows the unread count.
  • 🟢 The section is available even before you create a project.

6Project, filter and loading

Navigating the feed with several projects:

  • 📁 A project-related notification shows a chip with its name next to the title — it's clear which one it's about.
  • 🔍 At the top there's a project filter: pick a project to see only its notifications (or «All projects»).
  • 🎛️ Next to it — a type filter: ✅ success, ℹ️ info, ⚠️ warnings and errors (or «All»). Handy to quickly find, say, only model errors.
  • 🔁 The feed loads infinitely as you scroll — older notifications are fetched automatically.

7Email notifications

If an email is set in «Профиль», important problems (model errors, limits reached, token overspend) are also sent by email:

  • 🔒 No spam: an email is sent only when a NEW problem appears (repeats just bump the notification counter).
  • ✉️ A welcome email is sent on sign-up.
  • ⚙️ Emails arrive if email sending is configured in the service.

8Email confirmation

Emails are sent only to a CONFIRMED address:

  • 🟢 Yandex sign-in — the email is captured automatically and treated as confirmed.
  • 📝 Telegram sign-in — no address is shared, so on first sign-in the service asks for it in a friendly dialog.
  • 🔗 After you save an address, a confirmation link is emailed: follow it (valid for 24 hours, single use) — the address becomes confirmed and you land in the dashboard.
  • ⏳ While unconfirmed, «Профиль» shows a ⏳ status and a «Resend» button.

Didn't find an answer? Write to us — we'll help.

Contact support