Users
The accounts on this engine. Each owns its own VMs, images and networks, within the quotas it is given; an administrator sees and manages everything.
Add user
Creates an account on this engine. On a linked engine accounts can also come from the registry, where the same person may have access to more than one engine.
Username
What the account is known by, and what it signs in with. An email address is usual, and is what the registry expects on a linked engine.
Full name
The person behind the account, shown where an owner is named.
Where alerts about this account's VMs are sent - monitoring, backups, quota warnings.
Password
The account's own password. Left empty on a linked engine, the account signs in with its registry password instead.
Set password
An administrator can give a user a new password directly, from Set password in
the user's details - for when the reset link would not reach them, say. It is
typed twice, takes effect at once, and no email is sent, so tell them yourself.
On an engine linked to the registry it becomes their registry password too, with
the next account sync. Reset password instead emails them a link to choose one
themselves. From the command line: keal users passwd USERNAME.
Role
What the account may do: administrator, manager, user or read-only, in descending order of reach.
- Administrator - everything on this engine, including other accounts and the engine's own settings.
- Manager - manages the accounts below it, but not the engine.
- User - its own VMs, images and networks.
- Read-only - sees its own things and changes none of them.
Quotas
The ceiling on what an account may use: memory, processors, storage, public addresses. An action that would take an account past its quota is refused rather than queued.
On an engine linked to the registry, the quotas are set there, by its administrators, and come here with the account. They are shown here but not changed here; one the registry does not set is the engine's default.
Usage
What the account has now, against its quotas: how many of its VMs are running and how many it has, and the vCPUs, memory, shared storage and node storage it uses. The figures are the same as on the account's own Home, so they follow what its VMs and images hold rather than what is busy at this moment.
Accounts
Other accounts this one may switch to, and act as, from the user menu - a team account several people share, say, or a customer's account its operator looks after. Only an administrator gives and takes them away: add one from the list at the end, choose what it may do there, or take it away again with its cross.
- User - uses the account as its owner does.
- Read-only - sees the account and changes nothing in it.
- Administrator - administers the engine while acting as the account. Offered only to an account that is an administrator itself; anyone else would have it taken away on every request anyway.
What may be done is decided again on every request, by who really signed in, so taking an account away takes effect at once. Someone acting as an account when it is taken away is back on their own on their next step.