Before you begin
Confirm account, tenant and active role in the account menu. Inspection requires view permission; changing records requires the specific management permission. A hidden or disabled action can reflect authorized scope; do not switch tenants to evade a denial. Work only with records in the workspace you are allowed to administer.
Procedure
- Open Preferences and choose Notifications, Authentication, Limits, Email delivery or Data Cleanup.
- Confirm the scope before changing values.
- In Limits distinguish Platform defaults from tenant configuration.
- Save only permitted settings and verify persistence.
Behavior and limits
The five categories have different authorities. The account menu provides appearance, palette and authorized membership switches; these settings do not change permissions or contract. The interfaces support day and night themes.
Access to Preferences does not authorize global authentication or SMTP changes. Button availability depends on the active role. Do not change limits to evade a commercial or security restriction.
For Notifications distinguish Preview, Test channels and Save preferences. For Authentication test the saved configuration. For Data Cleanup inspect inventory and destructive confirmation. Each action reports a different outcome and requires its own verification.
Verify the result
After saving or confirming, reopen the detail and check the state reported by the server. Distinguish an accepted request from a completed operation and retain only minimal evidence without sensitive information. When an operation is pending, wait for its final state in the corresponding view before starting another action on the same object.
Laboratory example
Use the synthetic tenant documentation-lab and, where relevant, worker worker-demo-a. Note the previous state, perform one authorized action and compare the resulting state. These names illustrate the procedure; they do not identify production records or authorize creating cloud resources. For a review without changes, inspect the detail and cancel any open form.
If something fails
If a conflict appears, refresh the inventory and review current values before repeating. If the session expired, sign in and complete MFA when required. For a permission error, check the role and membership; for a provider error, inspect the operation and its safe message. Do not alter storage, revisions or controls to force an outcome.
Related reading
Interface language
In the user menu, select ES, EN or PT to change the interface language. The preference is saved to your profile and used by Dova and Administrator. If saving fails, the interface reports it and restores the previous choice. Available application labels change; artifact names, identities, fields, code and user data are not renamed. Style, palette and permissions retain their own configuration.