Notifications
An agency runs on things other people do: a task lands on a colleague, a project eats through its budget, somebody requests leave, your timesheet is still empty on Friday. schakl. turns those into a bell people actually read, and lets each person decide, per event, whether it also reaches their inbox or their Slack, and whether it arrives now or as one bundle a day.
Where to find it
Section titled “Where to find it”- The bell in the top bar, on every screen, with the unread count.
- Meldingen (Notifications), the full list, via “Alles bekijken” (View all) in the bell.
- Instellingen → Meldingen (Settings → Notifications), under “Mijn instellingen” (My settings): your own preferences, your own channels and Browsermeldingen (browser notifications) per device. Every member has this screen.
- Instellingen → Standaardmeldingen (Settings → Notification defaults), in the group “Communicatie & koppelingen” (Communication & integrations): what everyone inherits, plus the organisation’s shared channels. Admins only.
The bell and the list
Section titled “The bell and the list”The bell shows your most recent unread items, with Alles gelezen (Mark all read), Meldingsinstellingen (Notification settings) and Alles bekijken. The Meldingen screen has the columns Melding (Notification), Onderwerp (Subject), Door (By) and Wanneer (When), grouped per day (Vandaag, Gisteren). You filter on Alles / Ongelezen (All / Unread) and by record type (Taak, Project, Klant, Verlof, Urenregistratie, Contactmoment). Each row has Markeer als gelezen and back again; the top of the list carries Alles als gelezen markeren.
Opening a notification takes you to the record it is about and marks it read (one you open in a background tab stays unread). If it is about a comment on a task, the task opens on exactly that comment, with folded comments unfolded and the reply box ready underneath. A timesheet reminder opens the week that was still empty.
What you get told about
Section titled “What you get told about”The events are grouped the way the settings screen groups them. Which ones you see depends on the modules your organisation runs: without the leave module there are no leave rows.
| Group | For example |
|---|---|
| Taken (11) | Someone @mentions me in a comment, someone replies to my comment, an e-mail I sent to the task address became a task |
| Projecten (3) | A project is eating its budget |
| Klanten (3) | A client changes status |
| Verlof (3) | Someone requests leave |
| Uren (2) | My timesheet is still empty |
| Contactmomenten (2) | An e-mail is waiting for my review |
| Vergaderingen (2) | The minutes of my recording are ready, or the recording never arrived |
| SnelStart (1) | Last night’s invoices did not reach the ledger |
An automation rule can also send a notification. That one is not in the table below: you switch a rule off in the rule itself.
The matrix: who gets what, and when
Section titled “The matrix: who gets what, and when”Under Instellingen → Meldingen, the section Per gebeurtenis (Per event) holds one row per event, with:
- In-app: an Aan (On) tick, a Bezorging (Delivery) and a Vertraging (min) (Delay in minutes).
- E-mail: a Bezorging and a Vertraging (min).
- Browser: browser notifications on the devices you switched on (see below).
- One column per channel you connected yourself.
- Waarde van (Value from): where this row’s value came from, as Standaard (Default), Organisatie (Organisation) or Eigen instelling (Your setting). Terug naar overgenomen (Reset to inherited) drops your own override again.
Delivery is always Uit (Off), Direct (Immediately), Elk uur (Hourly), Dagelijks overzicht (Daily digest) or Wekelijks overzicht (Weekly digest). “Alles instellen…” (Set all…) above a channel column sets that whole column at once; Alle e-mail instellen op and Alle browsermeldingen instellen op do it for the e-mail and the browser column.
By default everything is on in-app. A short list arrives immediately (assignments, @mentions, a reply to your own comment, overdue tasks, tasks scheduled for you, the task address’s confirmation, all three leave events, an e-mail waiting for review and meeting minutes that are ready); the rest lands in the daily digest at 08:00 on your organisation’s own clock (Instellingen → Huisstijl → Tijdzone, Settings → Branding → Timezone). Browser notifications follow the same list: what arrives immediately also goes to your device, the daily digest does not. E-mail is off until somebody switches it on, with one exception: meeting minutes that are ready (or a recording that never arrived) mail at once by default, because whoever recorded is often no longer at their desk.
The Algemeen (General) section holds Bijna verlopen (dagen) (Due soon, in days; 3 by default), Stille uren vanaf / tot (Quiet hours from / until), the E-mailschema (E-mail digest schedule) and the Schema browsermeldingen (browser digest schedule): the Tijd (Time) and Dag (Day) your daily and weekly digests leave.
Quiet hours apply to e-mail, chat channels and browser notifications: whatever falls inside them waits until they are over, on your organisation’s clock, including a window that wraps midnight. The bell is left alone; it interrupts nobody anyway.
Browser notifications
Section titled “Browser notifications”A browser notification reaches your phone or a closed laptop lid, even when schakl. is not open. You switch it on per device under Instellingen → Meldingen → Browsermeldingen → Aanzetten op dit apparaat (switch on for this device); the browser then asks for permission itself. That is the choice: from then on the urgent events (the list above that arrives immediately) reach that device, and the Browser column adjusts it per event.
- Test versturen (send test) sends a test notification to all your devices.
- Je apparaten (your devices) shows where it is on, with Laatst gezien (last seen), and Verwijderen removes a device.
- On iPhone and iPad it only works in the installed app: add schakl. to your home screen first.
- A digest is one message here too, not one per device per event. A device you threw away is cleaned up on its own.
Connecting a channel of your own
Section titled “Connecting a channel of your own”- Go to Instellingen → Meldingen → Kanalen (Channels) → Kanaal toevoegen (Add channel).
- Give it a Naam (Name) and pick the kind.
- Paste what the provider actually gives you; schakl. converts it for you.
- Press Testen (Test). On success it reads “Testbericht afgeleverd”; otherwise you see the provider’s own error.
- Set the hour and the weekday this channel’s digests leave, on the channel itself.
- Go back to the matrix and set a delivery in the new column for the events you want sent there.
| Kind | What you paste |
|---|---|
| an e-mail address; sent through your organisation’s e-mail transport | |
| Slack | the URL of an Incoming Webhook for that channel |
| Microsoft Teams | the URL of an Incoming Webhook connector on that channel |
| Google Chat | the space’s webhook URL |
| Discord | the webhook URL from channel settings → Integrations |
| Telegram | a Bot-token from @BotFather and the Chat-ID |
| Webhook | an http(s) URL; every notification is POSTed there as JSON |
| E-mail (Apprise) / Overig (Apprise-URL) | a bare Apprise URL, for anything else Apprise supports |
A freshly connected channel stays silent until you route it in the matrix. That is deliberate: connecting a channel must not start buzzing somebody’s phone on its own.
Setting it for the whole organisation
Section titled “Setting it for the whole organisation”Instellingen → Standaardmeldingen carries the same matrix, but as the default everyone inherits until they change it themselves. It is also where you connect the shared channels: the team’s Slack or Teams channel, a group mailbox, a webhook into your own flow. Each gets its own column, so “#crm gets new clients immediately and everything else once a day” is simply something you set.
Permissions
Section titled “Permissions”| Permission | What it opens | Default |
|---|---|---|
notifications.notification.read | The bell, the list and reading your own preferences | Everyone |
notifications.notification.write | Marking read and saving your own preferences | Everyone |
notifications.channels.manage_own | Connecting your own channels | Administrator and Member |
notifications.defaults.manage | Instellingen → Standaardmeldingen | Administrator |
notifications.channels.manage | The organisation’s shared channels | Administrator |
Routing a shared channel takes both admin permissions at once: what lands in the team channel is a decision the organisation makes, not whoever last opened their own settings.
Good to know
Section titled “Good to know”- Credentials and webhook URLs are stored encrypted and never shown again; you only ever see a redacted preview. A webhook aimed at a private or local address is refused.
- If a delivery fails, the whole bundle stays pending with the provider’s own error recorded on it, and is retried at growing intervals. Half a digest sent is not a state that exists.
- The E-mail kind rides your organisation’s e-mail transport (Instellingen → E-mail), so it does nothing until that is configured.
- Resolving the underlying item resolves the notification: a decided leave request, a reviewed e-mail or a finished task that was due soon or overdue stops asking, for everyone who never opened it.
- A digest carries only what is still active: whatever you already read in-app, or what has been resolved meanwhile, is not sent out afterwards by e-mail or browser notification. If everything has been read, nothing is sent.
- A client’s contact person only hears about a task they may see: when they are mentioned in a comment, or when a task assigned to them is commented on. A client login gets that by e-mail at once by default, because the bell is not where a client lives.
- Notifications are part of the core and need no licence key. There is no SMS and no snooze; SMS exists only as a second factor at sign-in.