What you’ll learn

Explain the operational control purpose behind email notification settings

Configure tenant settings, defaults, notifications, and user profiles

Handle user lifecycle events, service health jobs, and log cleanups

Prepare and import standard templates, tickets, and search configurations

Lesson 1 of 3 Reading 12 min

Configure SMTP profiles

Email Notification Settings focuses on email reminder cadences, module-level notification emails, and SMTP/deliverability logs. In AWRA, administration and platform settings are key to organizing workflows, configuring user lifecycles, and ensuring system service health.

The main objective is operational efficiency. Admins should know how to establish standard settings, delegate roles, design notifications, and monitor queue jobs.

In practice, an admin sets a daily reminder cadence for overdue approvals, checks SMTP connection health, and reviews deliverability logs.

Email settings path

Connect

Verify SMTP server details and delivery certificates.

Configure

Define which events trigger automated module emails.

Schedule

Set the reminder cadence for pending system tasks.

Monitor

Check deliverability rates and fix soft or hard bounces.

Control model

Tenant configurations should remain consistent across branches.
User profiles and lifecycles require strict status updates.
Service health monitoring prevents data synchronization issues.
System templates and log reviews support ongoing audits.

Lesson 2 of 3 Workshop 14 min

Set reminder frequencies

The operating routine is to verify SMTP configurations, set reminder cadences, inspect email logs, and run deliverability checks. This keeps settings updates structured and ensures dependencies are validated before applying changes.

Before taking action, check SMTP settings, deliverability logs, bounce registers, queue statuses, and reminder timelines. These steps confirm that updates match configuration rules and do not affect active module functions.

An administrator can verify active settings or inspect jobs directly from indexes, dashboard catalogs, or email SMTP connection test blocks.

Deliverability guide

Signal	Check	Action
Email bounce detected	Check recipient email address	Flag address and notify user
SMTP connection error	Inspect mail server settings	Verify credentials and trigger test send
Reminder delays	Check queue worker status	Restart queue workers and monitor
Overdue alert spam	Review reminder cadence settings	Extend alert intervals in config

Response decisions

Set settings locks to prevent unauthorized updates.
Schedule notifications and digests to minimize noise.
Run template validation checks before bulk imports.
Escalate job failures or database errors immediately.

Lesson 3 of 3 Practice 14 min

Check delivery reports

Platform and configuration actions should leave proof. Useful evidence includes SMTP test connection reports, deliverability logs, bounce histories, and queue statistics, which helps track setup revisions, import counts, and system health status.

Management should review configuration patterns: repeated user lockouts, high queue processing times, or settings override requests often point to training or scaling needs.

In practice, closure means SMTP is connected, cadences are configured, and email logs confirm successful deliveries.

Email admin checklist

SMTP parameters are verified

Reminder cadences are set

Bounce reports are reviewed

Queue worker is active

Test message is delivered

Platform proof

Maintain a history log of all tenant setting updates.
Verify import validations to confirm column alignments.
Audit search speeds and log directories on a set cadence.
Confirm failed jobs are retried or archived with comments.

| AWRA OpsHub

Email Notification Settings

What you’ll learn

Course content

Configure SMTP profiles

Set reminder frequencies

Check delivery reports

Finished the material?

More in this path

Workflow Builder Basics

Approval Workflows

Security & Data Protection

Need a quick answer while you read?

AwraIQ