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 Audit and use search and filters to find the event.
- In View details inspect action, actor, timestamp and related subject.
- Open the corresponding screen to confirm its current state and record only the necessary evidence.
Behavior and limits
Events help correlate administrative changes. Pagination and columns change presentation, not the record. Exports must be limited to the authorized purpose.
An audit entry alone does not prove that a provider completed a VM operation, a payment settled or an execution produced the right result. Protect identities and sensitive content.
To investigate a role change, correlate the event with Users and Roles & permissions. For infrastructure inspect Cloud workers; for executions inspect Monitor. Preserve the distinction between the event’s historical state and the object’s current state.
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
Environment context
Before using this module, confirm Tenant, Domain and Environment in the user menu. The initial environment is Development. Module, Domain and environment capabilities apply together; Production is read only without explicit authorization. Switching the selector does not move artifacts or publish or execute their data. See environments and recovery and environment promotion.