Setting up personal and team notifications

Use Settings → Notifications to choose which Cedros updates you receive and where they arrive. You can send your own alerts to email, Slack, Discord, or Telegram, and administrators can route site and customer alerts to shared destinations.

This guide covers the recommended setup, individual alert choices, quiet hours, and delivery checks. Changes save automatically; wait for the save indicator to confirm that they are saved before leaving the page or sending a test.

Choose personal or team delivery

Personal notifications follow the signed-in user's preferences. Shared site and customer notifications follow the site's routes. A shared destination sends to the address or chat you select; it does not automatically send a separate message to every team member.

For example, you might receive your own assignments by email while sending new form submissions to a shared support inbox. Connecting the inbox and choosing the form-submission alert are separate parts of that setup.

You can manage your own notifications when you have access to this page. Changing shared destinations and site/customer alerts requires permission to edit site settings. If you cannot see those controls, ask an administrator to configure the shared route. See Understanding roles and permissions.

Before starting, have your receiving email address or the connection details for your chosen chat service ready. Email also needs working outgoing delivery on the site; see Setting up outgoing email delivery.

Start with recommended notifications

1. Open Settings → Notifications and wait for any pending changes to finish saving.
2. Select Enable recommended notifications. This opens a review; opening it does not change your settings.
3. Check each group's proposed alerts, whether they will turn on or off, and their receiving destinations. Expand Routine activity to review the updates that will be turned off.
4. If asked, confirm Send notifications to this email. Read whether that address will receive your activity, site/customer activity, or both. Check any missing-destination warnings before continuing.
5. Select Apply recommended setup, then wait for the settings to save. Check What will notify you to confirm the resulting alerts and recipients.

The recommended setup enables customer inquiries, assignments, review requests, and problems needing attention. It turns off routine completions and general updates. Job and routine failures are separate from successful completions, so you can receive problem alerts without subscribing to every successful run.

Working routes keep their recipients. Existing quiet hours and importance limits also stay in place. Applying this setup can change existing alert switches, so review the proposed changes even if you have already configured notifications. Cancel the review if you want to keep the current setup.

Connect a destination

1. Find Send notifications to. For a shared destination, an administrator can expand Recipients for site and customer activity.
2. Choose email, Slack, Discord, or Telegram and open its connection dialog. Follow the provider guidance shown there.
3. Enter the receiving address or connection details. Give chat destinations a clear name so you can recognize them in alert summaries.
4. Confirm the connection and wait for the settings to save. Return to What will notify you to choose which alerts should reach it.

Opening a connection dialog does not save it. Confirm the dialog to apply its changes; if you cancel after editing, Cedros asks whether to discard those edits. Webhook URLs and bot tokens are credentials: keep them out of public documents and screenshots.

Email

Enter the receiving address. Use my email prefills your account email so you can confirm it. This is the destination for the notification, not a replacement for the site's outgoing mail setup.

To add another receiving address for your own alerts, use Add email recipients for your activity. Adding an address alone does not subscribe it to alerts: select it for the appropriate alerts afterward.

Slack or Discord

Use an incoming webhook URL for the channel where messages should arrive. Confirm the destination in the provider's setup guidance before saving. Use a recognizable name, such as “Support alerts,” so shared routes are easy to review.

Telegram

Enter the bot token and the chat ID requested by the connection dialog. Confirm that the bot can send to that chat. The bot token identifies the sending bot; the chat ID identifies the receiving destination. A valid-looking token alone does not prove that delivery will work.

Choose alerts and recipients

1. Under What will notify you, expand the group containing the update you need. Each group offers Customize alerts and recipients.
2. Check the scope: For your assignments and activity controls your own alerts; For site and customer activity controls shared routes.
3. Turn on the specific alert. If Cedros asks for a destination, connect one before continuing.
4. Review the alert's recipients. For personal alerts, use Send to to select the connected destinations that should receive that update. For shared alerts, check the route's selected destinations and any importance setting.
5. Wait for the save indicator, then check the group's summary and expanded routing list. An enabled alert with no selected or working destination still needs attention.

The groups organize different kinds of updates:

• Problems needing attention contains site, security, delivery, and usage issues, including available job-failure alerts.
• Customers needing a response contains inquiries, support messages, and bookings.
• Work needing your attention contains assignments, reviews, and assistant responses.
• Routine activity contains completions and general updates.

Available alerts depend on your site's features and installed extensions. The group summary shows how many alerts are on and their destinations. If it says recipients vary by alert, expand the group to inspect each route rather than assuming every enabled alert goes to every listed destination.

For a support workflow, check the shared form-submission and support-chat routes separately. A notification directs someone to the work; it does not answer the customer. See Reviewing and managing form submissions and Taking over a support conversation.

Set importance filters and quiet hours

Expand Timing and importance. Your personal policy and the site/customer policy are separate. Changing your own policy does not change shared delivery for the rest of the site.

1. In the correct policy, use Send alerts for to choose All alerts, Important and urgent alerts, or Urgent alerts only.
2. Turn on Quiet hours if you want non-urgent alerts suppressed during a regular period.
3. Set Quiet hours start and Quiet hours end. Use different times and check the timezone displayed beside the control. An overnight period, such as 22:00 to 07:00, is supported.
4. Wait for the settings to save, then review any Delivery limits are active notice in the overview.

An alert can be enabled but filtered out by its importance threshold. Non-urgent deliveries during quiet hours are skipped, not stored for a morning digest. Urgent alerts can pass through quiet hours.

Older or individually configured routes can retain their own limits. If the overview still reports a limit after you change the main policy, read the destination named in the notice and inspect that route. Recommended setup does not clear these limits.

Test delivery and check the result

Send test sends a real message to the selected destination. Let recipients know when a shared channel is being tested. A test checks the destination; it does not prove that every alert is subscribed or that a future message will arrive.

1. Finish saving any changes. Send test is unavailable while settings are unsaved.
2. Select Send test beside the connected destination you want to check.
3. Expand View delivery activity and refresh it to inspect the new attempt and its destination results.
4. Check the receiving inbox or chat for the test message. For email, include spam, quarantine, and filtering rules in your check.
5. Review the relevant alert's switch and recipients under What will notify you. Confirm that delivery limits allow the updates you actually need.

Tests follow delivery policy too. Quiet hours or an importance threshold can cause a test to be skipped. Inspect the result before changing credentials or retrying repeatedly.

Delivery activity distinguishes Sending, Delivered, Partly delivered, Skipped, Unconfirmed, and failed attempts. A partial delivery means some destinations succeeded while others did not. Skipped calls for checking the recorded reason and delivery policy. Unconfirmed is not proof of delivery.

Each destination also shows its last attempt and time. A previous success is useful evidence, but it is not a guarantee about the next message. Administrators can retry eligible failed deliveries after correcting the cause; refresh delivery activity to check the new result.

Change or disconnect a destination

Use the destination's menu to edit its details or disconnect it. After an edit, wait for the save indicator and check the alerts that depend on that destination. Send a test when appropriate before relying on the new address or chat.

Disconnecting a destination affects routes that use it. Review What will notify you for alerts left without working recipients. Reconnecting a destination can restore delivery for routes that still reference it, so check those routes as well.

To stop only one kind of update, turn off that alert or remove the destination from that alert's recipients. Keep the destination connected if other alerts still need it.

Fix missing notifications or unsaved changes

An alert is on but nothing arrives. Expand its group and check the exact recipients, not just the group total. Resolve missing or incomplete destinations, then check importance limits, quiet hours, and delivery activity. Also confirm that the event you expect actually occurred.

Your alerts arrive, but the team receives nothing. Personal and shared routes are separate. Ask an administrator to check Recipients for site and customer activity and the relevant shared alert. Your personal email destination does not automatically become the team's recipient.

A new email address receives nothing. If it was added for your activity, select it under that alert's Send to controls. Connecting an address is not the same as subscribing it.

A destination test fails or remains unconfirmed. Read its delivery details. For email, check the site's outgoing delivery configuration and the receiving address. For chat services, check the destination, credentials, and provider access. Fix the reported cause before sending another test.

The save fails. Use Retry save after addressing the error, or Discard changes to return to saved settings. If Cedros reports that someone else changed the settings, discard your local changes to load the latest version, then make your edits again.

Delivery activity cannot load. Treat the load error as missing evidence, not an empty or successful history. Refresh or retry the history before using it to judge delivery.

You are ready when the intended alerts have working recipients, the settings are saved, the delivery policy fits your needs, and an appropriate test has reached the destination with a corresponding successful result.