← All documentationSearch guides

Understand roles and sensitive actions

Ownership, role and fresh authorization jointly govern actions.

  • All
  • Beginner
  • 1 min read
  • Reference: 101.18.15
  • Reviewed

Before you begin

Known role and an intended task.

Use the controls offered by your installed version and account permissions. This guide describes the workflow; it does not grant additional access.

Follow the steps

  1. Identify customer, root, staff, reseller or hosting-user responsibility.
  2. Use the workspace and ownership scope for that role.
  3. Complete required password/MFA checks for sensitive actions.
  4. Ask an authorized administrator to review missing access instead of sharing credentials.

Check the result

The intended identity performs only its permitted action.

If something goes wrong

Menu visibility is not authorization. Root terminals, destructive actions, credentials and private keys have stronger consequences.

Prepare useful details for support