Account context (root vs child account behavior)

VMease WebUI behavior is context-aware. The account currently in scope affects which admin actions are available, especially for setup and governance functions.

Back to documentation

Account context (root vs child account behavior)

What "Account Context" Means

  1. Root/Home context: top-level administrative scope for platform-level or parent-account operations.
  2. Child context: scoped view for a subordinate account/tenant.
  3. The UI determines context from the active account state and adapts available actions accordingly.

Why Context Matters

  1. Permissions alone are not the only control; some features also require a specific account context.
  2. Certain setup routes are explicitly restricted to home/root context.
  3. This prevents tenant-scoped sessions from performing parent-level platform actions.

Typical Context-Sensitive Behavior

  1. In root/home context, admins can access global setup and broader governance workflows.
  2. In child context, admins focus on tenant-scoped management and operations.
  3. Navigation and route access may differ between contexts even when the same role is assigned.

Operational Risks if Context Is Wrong

  1. Expected menu items are missing.
  2. Create/edit actions are unavailable despite role assignment.
  3. Direct links return unauthorized or inaccessible views.
  4. Changes are applied to the wrong account scope.

Admin Best Practices

  1. Confirm active account context before any create/edit/delete task.
  2. Perform platform-level setup only in root/home context.
  3. For "missing access" issues, validate context first, then RBAC permissions.
  4. Include account context in runbooks and change procedures.
  5. During troubleshooting, document both user role and active account context.
  1. Required context: Root/Home or Child
  2. Required permission(s): permission keys needed for the route/action

Ready to rethink private cloud?

Lower costs. Simplify operations. Deliver more.