Workspace Notifications
Notifications is the workspace control center for deciding which operational events notify your team and where those notifications go.
Open the workspace sidebar and select Notifications. The page has two tabs:
Workspace rules: configure routing for each supported event.Destinations: create and manage reusable notification endpoints.
People without permission to update workspace resources can still review the page, but its controls are read-only.
Understand the two configuration levels
Choose an event from Notification events. Each event is organized into:
Workspace rule: the shared routing rule for that event.Individual settings: event-specific overrides.
The current events use these levels differently:
| Event | Workspace rule | Individual settings |
|---|---|---|
Agent handoff |
Default destinations for every agent without an individual setting | Exceptions that use custom destinations or turn notifications off |
Form submitted |
Default destinations for every form without an individual setting | Exceptions that use custom destinations or turn notifications off |
Add a destination
Open Destinations and select Add destination. Available destination types are:
Slack incoming webhook: available for handoff and form submission events.Slack workflow webhook: available for form submission events.Email: available for handoff and form submission events.
Give the destination a recognizable name and enter its webhook URL or email address. Saved endpoints are masked in the interface.
Email destinations show Needs attention until the address is verified. Select Send verification email, open the verification link, and return to the page. For a ready webhook or verified email destination, use Send test notification before adding it to production rules.
Keep webhook URLs private
A Slack webhook URL is a secret. Do not paste it into public documents, issue comments, screenshots, or source code.
Route an event
Open Workspace rules, choose an event, and create or edit its workspace rule.
The rule editor only lists existing destinations that support the selected event. Select one or more destinations and save the rule. Clearing a checkbox does not delete the destination; it removes that routing relation only after you save the rule.
An enabled rule needs at least one selected destination, and at least one selected destination must currently be available. Disabled or unverified destinations are skipped until they become available again.
Configure form submission notifications
For Form submitted, every form without an individual setting uses the workspace rule. If the workspace rule is missing, disabled, or has no available destinations, those forms do not send notifications.
Add an individual setting when one form needs either of these exceptions:
Custom destinations: use only the selected existing destinations for this form. These destinations replace the workspace rule.Notifications off: do not send a notification when this form is submitted.
Changing an existing setting to Notifications off removes its custom destination selections. To resume custom notifications later, edit the setting and select the destinations again.
Each form can have one individual setting, and forms that already have one are not shown in the form selector. If every custom destination is unavailable, Codeer does not fall back to the workspace rule.
Delete an individual setting to return the form to the workspace rule. If the deleted setting had Notifications off, notifications resume when the workspace rule is available.
The Form Submissions page shows a read-only summary for the current filters. With All forms selected, it shows the workspace rule status and destinations plus the number of forms with individual settings. With a specific form selected, it shows whether the form uses the workspace default, custom destinations, or notifications off, together with the destinations that will actually receive the notification. Select Manage workspace notifications to open this event in Workspace Notifications. Destination creation and management are not available from the Form Submissions page.
Configure handoff notifications by agent
For Agent handoff, every agent without an individual setting uses the workspace rule automatically. Add an agent under Individual settings only when it needs one of these exceptions:
Custom destinations: use the selected existing destinations for this agent.Notifications off: do not send a notification for this agent's automatic handoff.
Changing an existing setting to Notifications off removes its custom destination selections. To resume custom notifications later, edit the setting and select the destinations again.
Select Add agent setting. In the same settings form, choose the agent, notification behavior, and destinations. Only agents without an individual setting are available.
Delete an individual setting to remove the exception and return the agent to the workspace rule. If the deleted setting had Notifications off, notifications resume when the workspace rule is available. If the workspace rule is missing, disabled, or has no available destinations, agents without an individual setting do not send notifications; delivery resumes when the rule becomes available.
Agent Editor shows the current mode and effective destinations as a read-only summary. Select Manage workspace notifications to open the Handoff event and the corresponding agent here.
Change or remove a shared destination
A destination can be reused by multiple rules and agent settings. Its Usage column shows the number of settings that use it. Select the count to see every usage location.
- Editing its endpoint or enabling or disabling it affects every listed use.
- Changing its type requires a new endpoint and may make it incompatible with existing rules.
- To stop one rule from using it, clear it in that rule and save the rule.
- To delete it, first remove it from every rule and agent setting, then delete it from
Destinations.
Creating, editing, enabling, disabling, testing, verifying, and deleting destinations only happens in the Destinations tab.