Notifications
Configure notification preferences, channels, and email templates.
Notification settings control how Agiled communicates with users and external channels.
Workspace notification settings decide which events can use which delivery channels. Personal notification settings decide what each user receives. Provider settings, such as SMTP and Slack webhook configuration, decide whether those channels can deliver successfully.
Notification Settings Areas
- Notifications: manage the workspace event/channel matrix and edit email templates for notification events.
- My Notifications: choose personal notification preferences for your own account.
- Notification Channels: configure delivery providers such as custom SMTP and Slack.
- Email Templates: edit reusable subject and body templates by locale.
User Notifications
Each user can manage personal notification preferences where available. These settings affect what the user receives without changing the whole workspace.
Channels
Workspace notification channels can include email, Slack, SMTP, or future delivery options depending on configuration. Test channels after saving them.
The channel matrix separates team notifications from client notifications where the event catalog supports it. Disable a channel only when you understand who will stop receiving that event.
Email Templates
Email templates control the text sent for common system and customer-facing events. Edit templates carefully and send test messages when available.
Use variables from the template editor instead of typing record details by hand. Reset a template when custom copy is outdated or when a broken variable prevents messages from rendering correctly.
Decide Who Should Receive Each Event
Review each event by audience:
- Internal events should notify the owner, assignee, reviewer, or team channel that can act on the update.
- Customer-facing events should use clear email copy and the correct sender or reply-to behavior.
- Finance, signing, booking, and support events should be tested end to end because customers may use the notification link to take action.
Do not enable every channel for every event. Too many notifications make users ignore the messages that need action.
Recommended Setup Order
- Configure delivery providers in Notification Channels.
- Test custom SMTP if you use it.
- Enable or disable event channels in Notifications.
- Review customer-facing email templates.
- Ask each user to adjust My Notifications for their own noise level.
- Trigger one safe event, such as a test assignment or internal workflow notification, and confirm delivery.
Test A Real Event
Provider tests only prove the channel can send. To prove a notification workflow, trigger a safe real event such as assigning an internal task, sending a test document, or creating a non-customer workflow alert.
Check the recipient, subject, message content, link, sender, Slack destination, and whether the event respects personal notification settings.
Reduce Notification Noise
If users ignore notifications, review noisy events before disabling whole channels. Keep urgent events such as assignments, approvals, payments, booking changes, and customer-facing failures easy to notice. Move informational updates to personal preferences or team channels when they do not require every user to act.
For finance, signing, booking, and support flows, verify the notification points to the correct public or internal record before relying on it for operations.
Troubleshooting
- If one user is missing notifications, check My Notifications and role permissions first.
- If every user is missing an email, check SMTP/Postmark delivery and the event/channel matrix.
- If Slack does not receive messages, verify the Slack webhook URL in notification channels.
- If customer email copy is wrong, edit the email template for the correct locale and event.