Email Traces en AUTOMY

Knowledge Center — Admin Studio

By Lily Dominguez Guerra · 2026-09-23

This guide explains the Email Traces option in AUTOMY Configuration from end to end: its purpose, the information it displays, how to use its controls, and what to validate before applying changes. 🧭 How to access Menu path Configuration → Monitoring and Audit → Email Traces Application route /configuration/email-traces ℹ️ Option and action visibility depends on the role, company, environment, plan, and tenant version. 🎯 Purpose and scope Review the status, type, recipient, and subject of emails processed by AUTOMY.

A successful status confirms recorded processing, not necessarily that the message was read.

Review provider, bounces, and the related request when applicable. 🖥️ Main screen Observed actions # Control Recommended use 1 Filter Use it only for the stated purpose and confirm the result before continuing. 2 Export Use it only for the stated purpose and confirm the result before continuing.

List information # Field or column How to interpret it 1 Status Value displayed for the record; use sorting or filters when available. 2 Created date Value displayed for the record; use sorting or filters when available. 3 Type Value displayed for the record; use sorting or filters when available. 4 To Value displayed for the record; use sorting or filters when available. 5 Subject Value displayed for the record; use sorting or filters when available. 🔎 Available filters Created date Type User Request Combine only the filters you need, select Apply , and use Clear filters before starting a different search. ✍️ How to work with this option The reviewed screen is read-only: it did not show an Add action.

Use filters and export only when available and authorized. ✅ Recommended procedure Confirm the active company and environment.

Define the purpose of the query or change and its owner.

Apply filters to check whether the record already exists or to narrow the period.

Review relationships, permissions, and dependencies before creating, editing, enabling, or disabling.

Save only after verifying required fields and scope.

Return to the list, filter again, and confirm the result.

For critical changes, review related traces or evidence. 🔐 Security and governance Apply least privilege and separation of duties.

Do not copy secrets, tokens, credentials, or personal data into names, descriptions, screenshots, or tickets.