Process Hub · Notifications and delivery

Configure process notification policies

Choose supported events, recipients, channels and timing, then release and verify the policy.

On this page

Before you start

  • Have Manage automations and publication access. Deploy the process and configure the real work/approval/schedule event first. Confirm channel setup with the administrator.

Follow these steps

Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.

  1. Open Settings → Process Hub → Workflows → Notifications. Create/edit a configuration and select the intended deployed process or reviewed set of processes.
  2. Name the configuration and keep Enabled after publication on when it should run. Select the event: Work assigned, Work reassigned, Approval requested, Approval approved, Approval rejected, Changes requested, Due soon, Overdue or Schedule created work.
  3. Choose recipients supported by that event/context: Submitter, Current actor, Assigned user, Approver, Requester, Specific profile user or Profile role. Select the actual profile user/role when required.
  4. Choose Priority and channels: In-app, Mobile push and/or Email. Review the generated message preview. The current guided policy uses fixed secure message copy; it does not offer free-form subject/body or field-value templates.
  5. Set timing for due events: Due soon uses Before due with an offset; Overdue uses After due. Other events are immediate. The underlying work must have a valid due date.
  6. Choose Individual notifications or One grouped notification for process notifications. Review shared impact when the configuration applies to more than one process.
    Notification policy showing channels, message, Assigned user recipient and immediate timing.View full size ↗
    Configure the event’s recipients and delivery channels. An Assigned user recipient needs an actual assignment when the event occurs.
  7. Save and validate the draft, then include it in the reviewed automation release. Trigger a new representative event, open Notification delivery and check the intended recipient’s inbox/channel.
    Notification operations view with a retryable failed outbox entry and delivery diagnostics.View full size ↗
    Inspect the outbox status and reference before retrying. Correct the underlying delivery problem and consider duplicate risk.
  8. Have the recipient review personal notification preferences, digest and quiet hours if delivery timing differs. Verify queued and delivered states separately.

Example: overdue Quality review

Give the Quality work item a real due time. Create an Overdue policy addressed to Assigned user, priority High, In-app plus Email if configured, with an After due offset agreed by the team. Test an overdue item in training and confirm the recipient can open its record.

Grouping versus personal digest

One grouped notification combines compatible events from the same worker batch for each resolved recipient. Profile, event, priority and channels must match. It is not one organisation-wide message and does not merge separate batches. Personal Digest is the user’s time-based delivery preference.

What you should see

A published enabled policy handles a supported new event and resolves the intended recipients/channels with traceable delivery results.

If something goes wrong

A saved policy sends nothing

Check successful publication, enabled state, event occurrence, recipient resolution, valid work due date for due events and the delivery worker. Saving does not send all old events.

You want a customer email address or a user-field recipient

Arbitrary external addresses and recipients taken directly from a user field or record owner are not supported in the current policy editor. Use its available profile recipient types.

The recipient gets two assignment messages

Lifecycle work creation already requires an In-app assignment notification. Check optional policies before adding another message for the same event.

You want a daily repeated reminder

The current guided policy does not author a general repeating-reminder schedule. Configure supported due offsets and test their actual events.

Need a hand?

Contact your organisation’s Emplyr administrator using your usual internal support channel.

How to ask for help