How VMease works

What VMease is

VMease is a web console for managing virtual machines and the infrastructure around them.

• It is an admin console — a single place to manage VMs, disks, storage, networks, firewalls, backups and more across your account.
• It sits on top of a Proxmox-based hypervisor platform, so you work with resources through the UI rather than touching the hypervisor directly.
• What you can see and do is shaped by two things: which account you are working in, and which permissions your role grants.

The async task model (why actions appear in Task Manager)

Most changes you request do not complete instantly in the browser — they are carried out in the background.

• When you request a change (start a VM, create a network, run a backup), the UI sends it to the API, which records what you asked for and queues a task.
• External workers pick up that task, perform the real operation on the hypervisor, and report the result back.
• You follow progress in the Task Manager (top bar): a task moves from pending to running to completed or failed.
• Because the work is asynchronous, a resource may briefly show a transitional state (for example "starting") until its task finishes.
• The UI only requests changes and reads status — it never performs the hypervisor work itself.

Accounts & scoping

Everything you see belongs to an account, and your view is limited to the account you are in.

• Resources are owned by an account. A root (parent) account can see itself and its tenant accounts; a tenant account sees only itself.
• Root users can switch down into a tenant to work inside it, then use Exit Account to return.
• Some areas are root-only — the Platform section (Clusters, Global VMs, and similar) — and are not available while you are inside a tenant.
• See the Multi-tenancy & account hierarchy (click here) concept for how the tree and switching work.

Permissions in brief

Alongside your account, a role determines which actions you are allowed to take.

• Access is granted through roles made up of permissions in the form category.module.action (for example, create a VM, or read backups).
• The UI hides or disables what your role does not allow — menu items, pages and buttons — but the API is the real gate that enforces it.
• If a page or action is missing, it usually means your role lacks that permission, or you are in an account that does not own the resource.
• Manage roles under Access Control → Roles; for the full model and the list of permissions, see the Permission model (click here) and Permissions reference (click here).