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 Users, find the account and choose View details.
- In New user or Edit user enter Name, Email, Tenant and the appropriate status.
- Use Select roles to assign the required responsibilities; save and inspect the record again.
Behavior and limits
Identity status, membership status and access readiness are different concepts. Changing memberships requires platform administration. An actor cannot delegate permissions it does not possess.
These actions cannot disable or demote your own account, or remove the last active platform administrator. Do not publish activation links or recovery material.
Also inspect Access and Last login. Never means no observed sign-in, not a failed execution. Presence does not grant access, and an active account may still require activation or MFA.
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
Identity and environments
Tenant and Environment selected in the user menu scope Cloud workers, their cloud connections, provisioning profiles, operations and dependency backups. A Domain declared on a resource must also match. Overview, resource history and operational Audit events respect this scope. Users, roles, tenants and billing retain their own authority: they are not independent copies per environment.