Yrka delivers notifications through the in-app notification center and, when configured by your organization, through external channels such as email digest, Web Push alerts, Slack webhooks, and SMS. The in-app notification bell is the canonical source for all Yrka notifications — if you are ever unsure whether a notification was sent, start there. External channels depend on provider setup and device permissions, and their delivery is not guaranteed by Yrka.Documentation Index
Fetch the complete documentation index at: https://docs.yrka.io/llms.txt
Use this file to discover all available pages before exploring further.
In-app notifications
Every notification Yrka generates appears in the in-app notification bell, accessible from the top navigation bar in both the admin and employee app. This is the most reliable place to check for any notification. From the notification panel you can:- View all unread notifications, most recent first
- Open the source record directly by clicking or tapping a notification (deep link)
- Mark individual notifications as read
- Dismiss notifications you no longer need
- See which workflow or event generated the notification
Notification preferences
You can control how you receive notifications from the notification preferences surface. Depending on your organization’s configuration, available options may include:- In-app only — notifications appear in the bell but are not sent to external channels
- Email digest — a batched summary delivered to your work email on an org-configured schedule
- Muted — specific event types are suppressed for your account
Notification routing rules — which events trigger which external channels — are organization-wide settings configured by admins. You can control your personal preference for receiving notifications, but you cannot change which events your organization routes to Slack, SMS, or other external pipes.
External delivery channels
Your organization can configure external notification delivery to the following channels. Each channel requires admin setup before it can deliver notifications.Email digest
Email digest
Email notifications are delivered to your work email address on file. Admins configure the delivery mode, timezone, quiet hours, hourly cap, and duplicate suppression window in Settings > Communications & Notifications.If you are not receiving email notifications:
- Confirm your work email address is correct in your profile
- Check whether quiet hours are active for your timezone
- Check your spam or junk folder
- Ask your admin to confirm the delivery mode is configured for your event type
Web Push / PWA alerts
Web Push / PWA alerts
Web Push notifications appear as device or browser alerts when you have the Yrka PWA installed or are using a supported browser. Web Push is per-device and per-browser profile — opting in on one device does not opt in other devices.iPhone and iPad users: You must add the Yrka PWA to your Home Screen before you can enable Web Push notifications. Requests for notification permission made before adding to Home Screen will not work.If Web Push is not working:
- Confirm you opted in from the notification preference surface in a supported browser or installed PWA
- Check your device or browser notification permissions for Yrka
- If the subscription shows as
expiredorrevoked, turn the device preference off and on again to refresh the subscription
Slack webhook
Slack webhook
Slack delivery requires an admin to configure a Slack webhook connection from the Integrations surface. Once connected, Yrka routes the configured event types to the configured Slack channel.If Slack notifications are missing:
- Ask your admin to confirm the Slack webhook connection is active in Integrations
- Check the delivery ledger in Integrations for
failedorprovider setup requiredstatus - Yrka does not have visibility into Slack-side delivery or channel membership — if the connection shows
sentin Yrka, the issue is Slack-side
SMS
SMS
SMS delivery requires admin setup of an SMS provider connection. Yrka routes configured event types to the phone number on file for the recipient.If SMS notifications are missing:
- Ask your admin to confirm the SMS provider connection is configured and active
- Confirm your phone number is correct in your profile
- SMS delivery depends on your carrier and the SMS provider; Yrka cannot guarantee delivery after the message leaves the configured pipe
Delivery status meanings
When reviewing notification delivery history in Integrations or the admin notification surface:| Status | What it means |
|---|---|
sent | The delivery path accepted the notification |
delivered | The recipient-visible destination recorded delivery (where that evidence exists) |
queued or processing | Delivery is still pending |
skipped | Delivery was intentionally suppressed (see common skip reasons below) |
failed | The delivery path could not complete |
provider setup required | External delivery needs configuration, authorization, or provider readiness |
expired or revoked | The Web Push subscription needs to be refreshed on the device |
- The recipient no longer has access to the source workflow
- The recipient disabled that event type in their preferences
- The recipient has no work email address on file
- Quiet hours are active for the recipient’s timezone
- An hourly email rate cap or duplicate suppression window applied
- The source workflow event still needs review before a notification is appropriate
Troubleshooting notification delivery
Check the in-app notification bell
Open the bell from the navigation bar. If the notification is there, the delivery event was generated. If it is not there, check the source workflow — the event may not have fired yet.
Confirm the source event exists
Open the workflow that should have triggered the notification — Messages, Tasks, Schedule, Timekeeping, Resources, or Profile — and confirm the event is in the expected state. A notification will not send for an event that has not been completed or published.
Confirm the recipient still has access
If a recipient’s app access was removed or their role changed after the event was generated, delivery may have been skipped.
Check external channel configuration
For email, Slack, SMS, or Web Push issues, confirm the channel is configured and active. Admins can check Integrations delivery history for status details.
Refresh an expired Web Push subscription
If Web Push notifications stopped working on a specific device, go to notification preferences on that device, turn Web Push off, then turn it back on. This refreshes the device subscription.
Escalate with delivery evidence
If a notification is in-app but not delivered externally, include the notification type, recipient, channel, in-app status, and external delivery status in your support request. Do not include Slack webhook URLs, SMS credentials, Web Push keys, or provider tokens in support notes.