Demo boundaries, email, and backups

Practice safely

• Use fictional examples. Do not upload real enrollment documents, identity records, employee files, or other sensitive information for a demonstration.
• Shared demo sign-ins are not individual production accounts. Other testers can use the same account and may change records.
• Do not assume every record already in the demo is safe to disclose. Do not copy unfamiliar personal details into screenshots or training materials.
• Read-only exercises do not require clicking Send, Save, Publish, Approve, or Reset. Do not send practice messages to real recipients.

Email is connected; mailbox administration is locked

The existing notifications account remains configured for application email functions. Its private mailbox administration panel is intentionally locked in the current demo, including for the owner through that panel. A staff role does not unlock it.

The lock does not disable all application email. Certain workflow actions can generate notifications. A saved record, portal message, or Sent indicator is not proof that a recipient received or read an external email. Report delivery concerns to the operator; do not reconnect or replace the account.

Dates and statuses

Sample deadlines and certification dates age with the calendar. An expired certification or passed training deadline can be expected behavior. Counts and dates in your screen may differ from screenshots.

Backups are manual

The current recovery export is a manually started, encrypted full data backup with a separate recovery key. It is not scheduled nightly. Application source is preserved separately. Backup and retention labels in Settings do not establish that automated backups are running.

The operator controls backup exports and recovery. Ordinary demo users should not change backup settings or attempt a restore. This user manual is not a disaster-recovery runbook.