Skip to main content

Notification Routing (The "Where")

📍 How to get here:

  1. Click on the Settings gear icon in your navigation menu.
  2. Select Organization Settings.
  3. Look at the left sidebar for the Notifications & Workflows section.

If you've ever wondered exactly where a specific alert goes when an approval happens, the Notification Routing tab is your answer.

(Image: Notification Routing) Notification Routing

How it works: This is a powerful switchboard that connects specific system events (triggered by your workflows) to specific people (your Personas) through active delivery channels (like Email or WhatsApp).

The Routing Matrix​

When you open the tab, you'll see a structured list of all Organization Modules (like Expenses, Timesheets, or HR). Under each module, you will find all the Events (templates) that can be sent out.

For every event, you can configure the routing logic:

  • Recipient Persona: Use the dropdown to select exactly who should receive this notification when the event occurs (e.g., selecting the "Finance Team" persona for an EXPENSE_APPROVED event).
  • Multiple Recipients: Do you need to notify both the employee and the finance department? You can click the Copy Row icon to duplicate an event rule, allowing you to assign a second Persona to the exact same event.
  • Delivery Channels: Next to the module and event, you'll see active channel indicators (like an Email icon or a WhatsApp icon). These automatically appear if you have configured those connections for the module.

Template Previews​

You don't have to guess what your emails will look like. The Notification Routing tab includes a powerful Template Previewer:

  1. Click the Eye (Preview) icon next to any event row.
  2. The system will open a modal showing exactly how the template will render.
  3. It automatically injects sample variables (like [expense_amount] or [user_name]) into the content so you can see the finalized HTML output or Raw Text.

💡 Pro-Tip: Workflow Integration

The true power of this system comes from integrating it with your dynamic Personas:

  • Routing Approvals: Bind an "Approval Required" event to the Current Approver persona. The system will automatically email whoever is currently holding the document in the workflow designer!
  • Routing Rejections: Bind a "Document Rejected" event to the Requestor persona. The system will immediately notify the person who submitted it.

The Grand Architecture​

To visualize how all these tabs work together:

  1. A user submits a request, triggering a Module State transition.
  2. This fires off an Approval Workflow assigned to specific Personas.
  3. As the workflow advances, the system generates events (like Approved or Rejected).
  4. Notification Routing intercepts these events, looks up the assigned Persona's resolution strategy to find the exact person, checks the active channel (like Email), and delivers the rendered template!