Notifications with YeshID
Last updated: June 23, 2026
Notifications keep your team and your people informed as work happens in YeshID — when a workflow kicks off, when someone has tasks waiting, and when work wraps up. There are two layers you can configure:
Org-level notification settings: account-wide preferences and the Slack/Teams connection, set once under Settings > Notifications.
Per-workflow notifications: the messages a specific workflow template sends, customized in the Notifications card of the workflow template builder.
Most teams set up the org-level basics once, then tune individual workflow templates as needed.
Organization notification settings
Go to Settings > Notifications to control account-wide preferences and connect a messaging tool. These apply across your whole YeshID account.
Setting | What it does |
|---|---|
Weekly YeshID admin emails | Sends admins a weekly digest of tasks and activity. |
AI weekly summary | Uses AI to generate the weekly admin email content. Requires weekly admin emails to be enabled. |
Notify me when YeshID detects that a new user has been created outside of YeshID | Alerts you when a new account appears in a connected app without going through YeshID. On by default. |
Notify me when YeshID detects a change in user status outside of YeshID | Alerts you when someone's status changes in a connected app outside of YeshID. On by default. |
The AI weekly summary option is available only available on paid plans.
Connecting Slack or Microsoft Teams
To send notifications through chat, connect a messaging bot from the same page:
YeshID Slack Bot: select Add to Slack and authorize. Under Notification channels, list the Slack channels the bot should post to. Don't see your channel? Invite the YeshID bot to it first.
YeshID Microsoft Teams Bot: select Add to Teams and provide the App ID from the YeshID app in your Teams Admin dashboard.
The channels you set here are your account's default channels — workflow announcements post to them unless a template overrides the target (see below).
Workflow notifications
Each workflow template has a Notifications card where you decide what that workflow sends, to whom, through which channel, and in what words. Settings live on the template and are snapshotted onto every workflow created from it, so a running workflow keeps its own notification behavior even if you later edit the template.
The three notifications
Notification | When it's sent | Who receives it |
|---|---|---|
Workflow Launch Announcement | When a workflow starts | Posted to your messaging channel (Slack/Teams) |
Task Assignment Notification | When a workflow starts | Each person who has tasks assigned to them |
Workflow Completion Notification | When the workflow completes | The workflow's owners |
Defaults by workflow type
The starting state of each notification depends on the type of workflow — for example, offboarding stays quiet by default so departures aren't broadcast, and completion notices are always opt-in:
Notification | Onboarding | Offboarding | Other types |
|---|---|---|---|
Workflow Launch Announcement | On | Off | On |
Task Assignment Notification | On | Off | On |
Workflow Completion Notification | Off | Off | Off |
You can override any of these per template.
What you can customize per notification
For each notification, the card gives you:
On/off toggle: turn the notification on or off for this template. A Default or Customized badge shows whether you've changed it.
Delivery Channels: choose where it's sent: Email, Slack, and/or Microsoft Teams. A chat channel only appears once that tool is connected. (The launch announcement is chat-only — it has no email option.)
Message Template: rewrite the message in your own words, up to 1,200 characters. Insert Variables (see below) by clicking the chips, or use Reset to Default to restore the built-in wording.
Post to channels (launch announcement only): target specific Slack/Teams channels for this template instead of your account defaults. Leave empty to use your org's default channels.
Message variables
When customizing a message, insert these placeholders, and YeshID fills them in when the notification sends:
Variable | Inserts |
|---|---|
| Workflow name |
| Link to the workflow in YeshID |
| Subject's first name |
| Subject's last name |
| Subject's email |
| Workflow date |
| Number of assigned tasks (Task Assignment Notification only) |
You can also reference a workflow's own inputs with {{arg:<name>}}.
How to customize a workflow's notifications
Open the workflow template you want to change and find the Notifications card.
For each notification, set the on/off toggle to match what you want that workflow to send.
Under Delivery Channels, pick Email, Slack, and/or Microsoft Teams. Connect a messaging tool first under Settings > Notifications if the chat options aren't showing.
Optionally edit the Message Template — click Variables to insert placeholders, and keep it under 1,200 characters. Use Reset to Default to undo.
For the Workflow Launch Announcement, optionally use Post to channels to send to specific Slack/Teams channels instead of your defaults.
Save the template. New workflows created from it will use these settings; workflows already running keep the settings they were created with.
Good to know
Connect chat before relying on it. If a chat notification is on but no messaging tool is connected, it simply won't send — YeshID flags this on the card: "This announcement is on, but won't be sent until you connect Slack or Microsoft Teams in Settings → Notifications."
Completion notices are opt-in. Turn on Workflow Completion Notification per template if owners want a heads-up when work finishes.
Offboarding is quiet by default. Both start-of-workflow notifications are off for offboarding so departures aren't announced — turn them on deliberately if that's what you want.
Edits don't affect in-flight workflows. Because settings are snapshotted at creation, changing a template updates future workflows, not ones already running.