Accounts

Administrators, resellers and users, staff roles, customer teams, branding, languages, sign-in security and what customers may do.

VMStack has three levels of account: administrators (staff), resellers and users (customers). Nobody signs up: every account is created by whoever manages it, in the panel, through the API or by a billing module.

What an account can see follows from its level. What it may do is narrowed further by staff roles (for administrators), team roles (for people working inside a customer's account) and customer switches (on plans, accounts and servers).

  • Account types: levels, reseller pools, creating, suspending and signing in as an account.
  • Staff roles: Support, Read-only and your own roles for administrators.
  • Teams: customers inviting colleagues with a role.
  • Branding: your own name, logo and colours, and a reseller's own brand and mail.
  • Languages: the eleven languages the panel ships with.
  • Sign-in security: two-factor, passkeys, bans, allowed addresses, sessions and how to get back in.
  • Customer permissions: the switches that say what customers may do, customer setup, trials and reinstall limits.
  1. Account typesThe three account levels (administrator, reseller, user), reseller pools and plans, creating, suspending and deleting accounts, and signing in as one.
  2. Staff rolesGive administrators a role (Administrator, Support, Read-only or your own) that limits what they may do, with per-role session rules.
  3. TeamsLet a customer invite colleagues into its account with a role (Owner, Member, Billing, Read-only, Notifications only), and how staff manage teams.
  4. BrandingReplace the VMStack name, logo, colours and sign-in page with your own, and let resellers show their own brand, mail text and SMTP server.
  5. LanguagesThe panel's eleven interface languages, how the language of each account and its mail is chosen, and the panel default.
  6. Sign-in securityTwo-factor authentication, passkeys, bans after failed sign-ins, captcha, allowed addresses, session timeouts and how to unlock an account from the shell.
  7. Customer permissionsDecide per plan, account and server what customers may do, let them set up their own server, and set trials and reinstall limits.