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 Developer Tools and select the destination operating system.
- Inspect published availability, version, checksum and signing information for the exact package.
- Download, verify integrity and follow Quick start in an authorized environment.
- In API Keys create only the necessary scope and revoke the key when no longer needed.
Behavior and limits
The CLI package version can differ from the Dova version. Downloading a tool does not grant permissions. Keys retain their authorized tenant and role scope; they do not replace server checks.
Do not invent platform availability, URLs or signatures. Do not put keys in documentation, terminal history or source. A revoked or unverifiably bound key must not be recovered through manual storage changes.
Distinguish availability, integrity and signing: they are different properties. The destination machine may use a different operating system from the browser. Check command scope before execution and use instructions bundled with that exact package.
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.