Managed notification workflows

Understand the difference between personal notification preferences and team-level managed automations.

Updated2 min readplatform

Notification workflows are team-level automations. They are not currently a self-service feature in the SunrAI dashboard.

What you'll learn

  • What a notification workflow is and why it's not the same as your personal notification preferences
  • What a managed workflow can do
  • What Owners and Admins can configure today

Not the same as notification preferences

Notification preferences are stored for you within the current team: they control which supported channels you receive for each event. Notification workflows are team-level automation: an event may cause SunrAI to prepare a message for a defined audience and channel.

Changing your personal preferences does not create, edit, activate, or archive a team workflow.

The anatomy of a workflow

At a high level, a managed workflow has three parts:

  1. Trigger — a supported event, such as a task assignment or project status change.
  2. Rules — the team and event details that determine whether the workflow applies.
  3. Actions — one or more configured messages for supported recipients and channels.

The exact triggers, rules, recipients, timing, and channels must be reviewed before a workflow is activated.

What you can configure today

The dashboard currently exposes personal notification preferences, not a visual team-workflow builder. Use Settings → Notifications to configure your own supported channels for the current team.

Owners and Admins who need a team-level automation should contact support@sunrai.ai with:

  • The business event that should trigger it
  • The intended recipients
  • The requested channel and timing
  • An example message
  • Any compliance or consent requirements for customer-facing delivery

SunrAI will confirm whether the requested trigger and channel are supported and will arrange a controlled test before activation.

Verify a managed workflow

When support tells you a workflow is ready:

  1. Confirm the documented trigger, recipients, channel, and timing.
  2. Run the agreed test scenario with a non-customer test recipient.
  3. Confirm both the expected delivery and the absence of duplicate delivery.
  4. Ask support to activate the production configuration only after the test passes.

Troubleshooting

"I changed my preferences but the team workflow did not change." — This is expected. Preferences and managed workflows are separate settings.

"A test message did not arrive." — Confirm the test recipient and channel with support. For email, also check the verified address and spam folder. For browser notifications, check browser permission on that device.

"A live workflow sent the wrong message or recipient." — Contact support@sunrai.ai immediately with the team, approximate time, event, and channel. Do not include passwords, access tokens, or customer secrets.