> For the complete documentation index, see [llms.txt](https://docs.codemash.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codemash.io/norbix-cloud/notifications/server-events.md).

# Server Events

**Server Events** push real-time updates from your backend to connected clients the moment something happens — without polling and without running a separate WebSocket server. Delivery uses **SSE (Server-Sent Events)**, a web standard that works across web and mobile clients.

It is the real-time layer every other module can feed into: a [Database](/norbix-cloud/database.md) record change, a [Payments](/norbix-cloud/payments.md) event, the output of a [Code](/norbix-cloud/code.md) function — any of these can surface to a client in real time.

### How you target events

| Target               | Description                                  |
| -------------------- | -------------------------------------------- |
| **Broadcast**        | Sent to all connected clients in the project |
| **User-targeted**    | Sent to all sessions of a specific user      |
| **Session-targeted** | Sent to a single specific connection         |
| **Channel-based**    | Sent to all subscribers of a named channel   |

Clients can subscribe to channels and filter events by type or topic. Connection lifecycle (connect, disconnect, reconnect) is managed for you.

### Configure vs consume

* **In Norbix Cloud (Hub):** define channels, set subscription rules, and configure access control.
* **At runtime (API / SDKs):** your app subscribes to channels, receives live events, and can send targeted events.

### Events are moment-in-time

Server events are **volatile by design**: they are delivered in the moment and are not stored or replayable. They are notifications, not state — your data stays in the [Database](/norbix-cloud/database.md), and delivery history is visible in [Logs & Monitoring](/norbix-cloud/logs.md). If a client is offline, it simply reads current state when it reconnects.

### Typical uses

Live dashboards, chat and presence, progress of long-running jobs, real-time UI updates driven by [Database triggers](/other-topics/triggers.md), and AI-generated interfaces that need to react to data changes without round-tripping.