Configure Notification Channels

Notification channels decide where workspace notifications can be delivered. Personal notification settings decide which notifications each user receives.

Configure channels before relying on notification automations, customer emails, or Slack alerts. A notification event can be enabled in the matrix and still fail if the delivery provider is not configured.

Review Channels

1. Open Settings.
2. Go to Notification Channels.
3. Review the email provider status.
4. Configure custom SMTP if you do not want to use the default email provider.
5. Add a test recipient and test the SMTP connection.
6. Add a Slack webhook URL if Slack notifications are needed.
7. Save changes.

Use channel settings carefully. Disabling a workspace channel can affect multiple users and workflows.

Email Provider Settings

The email section shows whether the workspace is using the default provider or custom SMTP. Custom SMTP fields include:

• SMTP host.
• Port, commonly 587 for TLS or 465 for SSL.
• Encryption: TLS, SSL, or none.
• Username.
• Password.
• Test recipient.

Always test the SMTP connection after saving or changing credentials. Use a recipient that can confirm delivery quickly.

Slack Settings

Slack delivery uses a webhook URL and optional logo URL. Create the webhook in the Slack workspace/channel where notifications should appear, paste the webhook URL into Agiled, save, and then trigger a safe notification to confirm delivery.

Do not paste a personal or unrelated Slack webhook into a workspace-wide notification setting. Anyone who can trigger the enabled event may send messages to that Slack destination.

Channel Failure Recovery

When a provider fails, pause broad notification changes until you know whether the issue is credentials, provider delivery, event settings, or recipient preferences. Changing all events at once can hide the original problem.

For customer-facing email, keep a backup operating path such as resending from the record, copying the public link, or using a verified sender while SMTP is being repaired.

Provider Ownership

Assign an owner for each delivery provider. That owner should know where SMTP credentials, Slack webhook configuration, sending domains, and recovery access are managed.

Avoid using a personal mailbox, personal Slack app, or individual-only credential for workspace-wide notifications. If that person leaves, customer and team notifications can stop without a clear recovery path.

Push Notifications

The push notification section is reserved for future delivery behavior when the app exposes it. Use email and Slack for current notification delivery unless your workspace has another configured provider.

What To Check

• Important system notifications are still enabled.
• Finance, scheduling, and document notifications go to the right channels.
• Slack or external channels are connected before enabling them.
• Email delivery is configured before relying on email notifications.

Change Checklist

After changing channels:

1. Save the provider settings.
2. Test SMTP or trigger a safe Slack notification.
3. Open Notifications and confirm the event/channel matrix still matches the team’s desired behavior.
4. Ask one affected user to verify delivery.
5. Update internal operating notes if customers or finance messages depend on the changed provider.

Troubleshoot Delivery

If notifications are not delivered, separate provider failure from event configuration:

1. Test the provider connection.
2. Confirm the notification event is enabled for that channel.
3. Check the recipient's personal notification settings.
4. Trigger a safe event and inspect whether email or Slack received it.
5. Review spam, quarantine, bounced mail, or Slack channel permissions.

Related Docs

• My Notifications
• Email Template Settings
• Apps