Report Tokens en AUTOMY

Knowledge Center — Admin Studio

By Lily Dominguez Guerra · 2026-07-24

This guide explains the Report Tokens 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 → Reports → Report Tokens Application route /configuration/reports-tokens ℹ️ Option and action visibility depends on the role, company, environment, plan, and tenant version. 🎯 Purpose and scope Manage tokens that enable report connection or access scenarios according to type and context.

The token is a credential: never publish it in articles, screenshots, tickets, or repositories.

Limit scope, record an owner, and revoke or rotate it when no longer needed. 🖥️ Main screen Observed actions # Control Recommended use 1 Filter Use it only for the stated purpose and confirm the result before continuing. 2 Add Use it only for the stated purpose and confirm the result before continuing.

List information # Field or column How to interpret it 1 Enabled Value displayed for the record; use sorting or filters when available. 2 Type Value displayed for the record; use sorting or filters when available. 3 Report type Value displayed for the record; use sorting or filters when available. 4 Token Value displayed for the record; use sorting or filters when available. 5 Process Value displayed for the record; use sorting or filters when available. 6 Request Value displayed for the record; use sorting or filters when available. 7 Entity Value displayed for the record; use sorting or filters when available. 🔎 Available filters Type Report type Enabled Dynamic entity Process Request Created date Created by Combine only the filters you need, select Apply , and use Clear filters before starting a different search. ✍️ How to work with this option Fields marked with (*) are required.

Fields observed when adding # Field or column Recommended use 1 Type (*) Enter a value valid for the company and review relationships before saving. 2 Report type (*) Enter a value valid for the company and review relationships before saving. 3 Dynamic entity Enter a value valid for the company and review relationships before saving. 4 Enabled Enter a value valid for the company and review relationships before saving. ✅ 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.