> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wanhap.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Notifications
> Stay informed about post publishing, account issues, and team activity.
## What are notifications?
Wanhap sends notifications to keep you informed about important events — successful publishes, failures, account issues, and team activity. Notifications are delivered in real time so you can react quickly.
## Notification types
### Publishing
| Type | When it's sent | What it tells you |
| ---------------------------- | ---------------------------------------------------------- | ----------------------------------------------------------- |
| **Post published** | A post was published to all enabled platforms successfully | Which platforms were published with links to the live posts |
| **Post failed** | A post failed on every enabled platform | Which platforms failed and the error messages |
| **Post partially published** | A post published on some platforms but failed on others | Which platforms failed and the error messages |
### AI
| Type | When it's sent | What it tells you |
| -------------- | ----------------------------------------------------------------------------------- | --------------------------------------------------------- |
| **Post ready** | The AI **Create** flow finished generating a post (text + images) in the background | A link to the new draft so you can review and schedule it |
### Accounts
| Type | When it's sent | What it tells you |
| ------------------------ | --------------------------------------- | -------------------------------------------- |
| **Account disconnected** | A social account lost its authorization | Which account and platform need reconnection |
### Team
| Type | When it's sent | What it tells you |
| ------------------------ | ---------------------------------------------- | ----------------------------------------------------- |
| **Invite received** | You were invited to join a workspace | Who invited you and which workspace |
| **Member joined** | Someone accepted an invite to your workspace | Who joined and their role |
| **Member removed** | A member was removed from your workspace | Who was removed |
| **Mentioned in comment** | A teammate `@`-mentioned you in a post comment | The post, the commenter, and a snippet of the comment |
### Billing
| Type | When it's sent | What it tells you |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------- |
| **X publication credits exhausted** | Your [X publication credit balance](/knowledge-base/plans-and-billing#x-twitter-publication-credits) ran out | That X posts are blocked until you top up — other platforms are unaffected |
## Notification channels
| Channel | Description |
| ---------- | -------------------------------------------------------------------------------------------- |
| **In-app** | Bell icon in the top nav. Delivered in real time via Reverb (WebSockets) — no refresh needed |
| **Email** | Sent to the address on your Wanhap account, via the configured mailer (SendKit by default) |
In-app notifications are always created. Email is sent in addition to in-app for most types, with a couple of carve-outs:
* `mentioned_in_comment` — if you're online, only the in-app toast fires; if you're offline, you get both.
* `post_ready` — in-app only. The AI Create flow is short enough that a banner inside the app is all you need.
## Notification preferences
Go to **Settings > Notifications** to toggle which notifications you receive. Each toggle controls **email** for that notification type — in-app notifications are always created so you can catch up later from the bell.
Today the page exposes three toggles:
| Toggle | Controls email for |
| ------------------------ | --------------------------------------------------------------- |
| **Post published** | `post_published` |
| **Post failed** | `post_failed` (covers both full failures and partial publishes) |
| **Account disconnected** | `account_disconnected` |
`mentioned_in_comment`, `invite_received`, `member_joined`, `member_removed`, `post_ready`, and `x_publication_credits_exhausted` use sensible defaults today and aren't user-configurable yet.
Keep **Post failed** and **Account disconnected** emails on. They need immediate action and you might not be looking at the dashboard when they fire.
## Managing notifications
The notification center (bell icon) shows all your in-app notifications:
* **Mark as read** — Click a notification to mark it as read
* **Mark all as read** — Clear all unread notifications at once
* **Archive all** — Archive all notifications to start fresh
## FAQ
The workspace owner receives all publishing notifications (success and failure), regardless of who created or scheduled the post.
Yes. Go to **Settings > Notifications** and disable each notification type. In-app notifications will still appear in the notification center, but emails will stop.
In-app notifications are delivered in real-time via WebSockets. You'll see them appear instantly without refreshing the page. Emails are sent asynchronously via the queue worker.