Notifications and integrations
The panel tells you what just happened — no refreshing, no checking each module one by one. The bell in the top-right corner gathers events from across your company, and if you like, those same notifications can also land in Slack, Discord, Microsoft Teams or your own automation flow.
The in-panel bell
The bell icon in the top-right corner is your quick view of what is going on in the company. Click it and a list of recent events unfolds, for example:
- Finished generations — the material you ordered is ready.
- Scheduled publications — a scheduled post or send has gone out.
- Requests — for example a leave request waiting for a decision.
Clicking an event takes you straight to the right place in the panel, so you never have to hunt for it.
Info
Some events are only visible to people with the right role. A leave request awaiting approval appears to someone allowed to approve it — for anyone without that permission, the event simply never shows up. More in Roles and permissions.
The "read" state is separate for each person. When you mark notifications as read, they stay fresh for your colleagues until they see them for themselves. The bell is the one channel that always works inside the panel — it does not depend on any external connection.
External notification channels
If you would rather get notifications where your team already works, you can connect channels outside the panel. Your options:
| Channel | When it helps |
|---|---|
| Slack | Your team lives in Slack and wants events on a chosen channel |
| Discord | Your company communicates through Discord |
| Microsoft Teams | Your company works in the Microsoft ecosystem |
| Custom webhook | You want to wire events into your own automation flow, e.g. Make.com or n8n |
These channels are entirely on your side — your accounts, your tools. You can connect one, several or none and rely on the bell alone.
Wskazówka
The custom webhook is the most flexible option: connect it to a tool like Make.com or n8n and decide for yourself what happens next with an event — it lands in a spreadsheet, creates a task, triggers any scenario you like.
What we send outside
To external channels we send only the event title and a link back to the panel — never sensitive content. In Slack or Teams you will see that something happened and reach the details in one click, but the message itself carries no document text, no request contents, no personal data.
This is deliberate. External channels are a company-wide account with no role split, so the details — protected by permissions — stay in the panel. More on this approach in Security and GDPR.
Who configures channels
External channels are connected and enabled by someone with permission to manage settings for the company — usually a manager, administrator or owner. Receiving notifications in the bell, on the other hand, is available to anyone with access to the relevant area.
Uwaga
Do not see the section for connecting channels? Your role most likely does not include managing settings. Ask someone with that role for help, or reach out to your WebImpact manager.
Related pages
- Settings and branding — where company settings are managed in the panel.
- Security and GDPR — why only a title and a link go outside.
- Roles and permissions — who sees which events and who configures channels.