How to enable the Notification Center on the instance (root)
The Notification Center is the full Profile → Notifications experience (channels, notification types, system messages in chat, and reminders). It is turned on in instance settings and is available only to root administrators.
When you need this
- You want to replace the simplified profile notifications screen with the full Notification Center for all operators.
- You need the Notification settings page under Settings (mandatory channels/types, bot and scenario).
What to know
- Without the main flag, ticket/chat notification behaviour stays on the legacy path (socket-oriented). After you enable the Center, events are delivered through the notifications module to assignees and participants according to user settings.
- Names below match the switches as shown in the UI (the category and labels may appear in English in the interface).
- The second flag (extended types) is optional and is not recommended to enable “just in case” while CSAT (negative), SLA, and normatives flows are still being rolled out for your instance. Enable it only when your team confirms these types are fully supported and you agree with support/platform owners.
Before you start
You are logged in as root. You can open Instance settings in the Settings module (see also Configure instance parameters).
Step-by-step
1. Open instance feature toggles
- Open Settings (
/settings-page). - Open Instance settings.
- Scroll to the platform feature toggles block (the header often mentions Feature flags).
2. Enable the main flag
- Expand the Notifications category.
- Turn on Notification Center (technical key:
notification_center_enabled). - Changes are saved automatically when you toggle (same as other flags in this block).
- Reload the page if the UI does not pick up the change immediately.
3. Keep the second flag off (for now)
In the same Notifications category you will see NC: CSAT / SLA / Normatives settings (notification_center_extended_types_settings_enabled).
- Default rollout guidance: leave it off until extended notification types are confirmed for your instance and enabling the flag is agreed with your technical/support contact.
- While it is off, the related blocks in the operator profile stay read-only (as before extended types are fully adopted).
- When it is on, operators can edit channels for those types in the profile, and admins can mark them mandatory on the OP notification settings page only if those types are correctly wired for your instance.
What changes after Notification Center is enabled
- Operators see the full Notification Center under Profile → Notifications (tabs Channels, Notification types, System messages in chat, Reminders) instead of the simplified screen — see the Notification Center reference.
- Ticket and chat events (for example ticket updates, new chats, subject changes, comments) are produced through the notifications module and appear in the channels each user configured.
- Some duplicate success toasts may be suppressed when the same event is already covered by the Notification Center — this is expected.
- Users with operator panel settings rights get access to Notification settings at
/settings-page/op-settings/notificationsfor instance-wide policy (mandatory channels/types, bot wiring).
After enabling the flag, complete How to configure notifications for the instance (administrator) if you need mandatory channels, bot delivery, and so on.
Where to manage settings after enablement
| Role | Where in the UI | Documentation |
|---|---|---|
| Operator | Profile → Notifications (or user menu → Settings → Notifications) | Notification Center reference, short profile entry |
| OP administrator (not root) | Settings → operator panel settings subgroup → Notification settings | How to configure notifications for the instance |