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.
Account context (root vs child account behavior)
What "Account Context" Means
- Root/Home context: top-level administrative scope for platform-level or parent-account operations.
- Child context: scoped view for a subordinate account/tenant.
- The UI determines context from the active account state and adapts available actions accordingly.
Why Context Matters
- Permissions alone are not the only control; some features also require a specific account context.
- Certain setup routes are explicitly restricted to home/root context.
- This prevents tenant-scoped sessions from performing parent-level platform actions.
Typical Context-Sensitive Behavior
- In root/home context, admins can access global setup and broader governance workflows.
- In child context, admins focus on tenant-scoped management and operations.
- Navigation and route access may differ between contexts even when the same role is assigned.
Operational Risks if Context Is Wrong
- Expected menu items are missing.
- Create/edit actions are unavailable despite role assignment.
- Direct links return unauthorized or inaccessible views.
- Changes are applied to the wrong account scope.
Admin Best Practices
- Confirm active account context before any create/edit/delete task.
- Perform platform-level setup only in root/home context.
- For "missing access" issues, validate context first, then RBAC permissions.
- Include account context in runbooks and change procedures.
- During troubleshooting, document both user role and active account context.
Recommended Documentation Note
- Required context: Root/Home or Child
- Required permission(s): permission keys needed for the route/action
Ready to rethink private cloud?
Lower costs. Simplify operations. Deliver more.