Extra User Fields en AUTOMY
Knowledge Center — Admin Studio
By Lily Dominguez Guerra ·
This guide explains the Extra User Fields 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 → User Management → Extra User Fields Application route /configuration/extra-user-fields ℹ️ Option and action visibility depends on the role, company, environment, plan, and tenant version. 🎯 Purpose and scope Extend user profiles with additional attributes reusable across the platform.
The internal name appears in the list although it is not requested in the observed add form.
Do not store passwords, tokens, sensitive documents, or secrets in these fields. 🖥️ 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 Order Value displayed for the record; use sorting or filters when available. 2 Required Value displayed for the record; use sorting or filters when available. 3 Display text Value displayed for the record; use sorting or filters when available. 4 Internal name Value displayed for the record; use sorting or filters when available. 5 Type Value displayed for the record; use sorting or filters when available. 🔎 Available filters Type Created date Updated date 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 Order Enter a value valid for the company and review relationships before saving. 2 Display text Enter a value valid for the company and review relationships before saving. 3 Type Enter a value valid for the company and review relationships before saving. 4 Required 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.