Tenant user, administrator, or support operator
Tell people what needs attention and retain evidence of change
Notifications prompt attention; activity records explain changes. Keep those purposes separate. A notification may be read or dismissed, while an audit record should remain an objective reference for support and security.
Before you start
- A tenant user and at least one seeded workflow outcome.
- Mail or optional channels configured only if they will be tested.
#Configure useful notification behavior
Choose topics, channels, digest frequency, and critical-only behavior appropriate to the user’s role. Test in-app delivery first. Enable email, SMS, or WhatsApp only after provider setup and consent expectations are clear.
#Verify the Northstar owner notification
- Run the safe approved workflow path.
- Open the owner’s notification inbox.
- Confirm the title, workspace, related record, and action link.
- Mark it read and verify read state.
- Check activity and execution history for the underlying event.
#Share evidence without sharing secrets
For support, provide the workspace, approximate time, record or execution reference, and redacted error. Never send passwords, API keys, bearer tokens, webhook secrets, private attachment URLs, or raw customer data.
#Common mistakes
- Using notifications as the only execution evidence.
- Sending critical alerts only through an unverified external channel.
- Copying raw secrets into support notes.
#Verify the result
- The correct user receives the notification.
- Action links retain tenant context.
- Activity and execution references correlate.
- Shared support evidence is redacted.