Notification mapping

Notification mapping in Document360 lets you connect specific portal events to notification channels — such as email, Slack, or Microsoft Teams — so your team receives automatic alerts when content or settings change. Instead of manually checking for updates, you configure which events trigger alerts and which channels receive them, keeping contributors, reviewers, and admins aligned without additional overhead. Notification mapping is available in the Knowledge base portal under Settings > Notifications > Notification mapping.

When to use notification mapping

Use notification mapping when you need to:

• Keep a distributed content team in sync — when multiple contributors work across articles and categories, mapping events like article published or workflow status updated ensures no one misses a change they need to act on.
• Maintain an audit trail for security changes — when your knowledge base has strict access controls, mapping events in the Users & security settings module (role changes, SSO updates, IP restrictions) gives admins an automatic record of every change without manual log reviews.
• Reduce review bottlenecks — when articles go through an approval workflow, mapping workflow assignee and due date events to a team channel keeps reviewers accountable and deadlines visible without chasing people manually.

Before you begin

• You must have Owner or Admin role permissions to configure notification mapping.
• At least one notification channel (SMTP, Slack, Microsoft Teams, or another supported channel) must be configured before you can map events to it. See Setting up notification channels for setup instructions.

How to configure notification mapping

Enable and map notification events

1. Navigate to Settings () > Knowledge base portal in the left navigation bar.

2. In the left navigation pane, select Notifications.

3. Click the Notification mapping tab.

4. To enable all events at once, turn on the All events toggle.

5. To enable a specific module only, turn on that module's toggle.

6. To enable individual events within a module, expand the module accordion and turn on each event toggle you need.

   Example: Turn on the Documentation editor module toggle to receive all editor-related notifications. Alternatively, expand the module and enable only the Article published toggle to receive notifications for that specific event.

7. Click Map to channel to assign channels to events in bulk, or click the icon next to any individual event to assign a channel to that event alone.

Enable the analytics weekly report

Project owners can subscribe to a weekly analytics report delivered by email.

1. Navigate to Settings () > Knowledge base portal in the left navigation bar.
2. In the left navigation pane, select Notifications.
3. Click the Notification mapping tab.
4. Expand the Analytics accordion and turn on the Analytics weekly mail toggle.

Notification events reference

The following modules list all available notification events. Expand each module to view its events.

Best practices

• Enable events selectively — turning on all events can create notification fatigue. Enable only the events that require immediate action from your team.
• Map critical security events first — prioritise events in the Users & security settings module (role changes, SSO updates, IP restrictions) to maintain an audit trail.
• Use dedicated channels per module — map documentation events to a content team channel and security events to an admin channel to reduce noise.
• Re-map events immediately when a channel is deleted — if a notification channel is removed, any events mapped to it silently stop delivering. Check and reassign affected events as soon as a channel is deleted.

FAQ