Back to help center
    Account and billing

    User management — teams, roles and contacts

    How vBoxx organises companies, members and the roles that gate the portal.

    5 min read

    How teams work

    Your vBoxx account is organised around teams. A team represents a company or organisation and contains everything: services, orders, invoices, payment methods and people. If you manage hosting for several organisations, you can be a member of multiple teams and switch between them in the portal.

    Two kinds of people belong to a team:

    • Members — have a portal login. They can manage servers, place orders or view invoices, depending on the roles you give them.
    • Contacts — no portal access. Just email addresses that receive notifications, e.g. an accounting mailbox that should receive invoice copies, or a colleague that wants status emails.

    Creating a new team

    From Settings → Team → Create team. Only do this when you actually need a separate organisation with its own billing and services. Teams are fully independent. If you only want to give a colleague access to your existing setup, invite them as a member instead.

    Roles

    Owner

    Whoever created the team. Full access to everything, the only role that can change other members' roles, enable/disable members, or transfer ownership (via support). The owner cannot be removed or disabled.

    Assignable roles

    RoleWhat they can do
    AdminEverything except changing the owner.
    BillingView and pay invoices, manage payment methods, change billing details.
    OperatorManage services: power actions, JetKVM, tickets. No billing.
    ViewerRead-only access to services and tickets.
    DeveloperManage API tokens for the team.

    A member can hold any combination of roles. Effective permissions are the union.

    Contacts

    Add contacts under Settings → Team → Contacts. Pick the categories of email each contact should receive: invoices, service status, security advisories, maintenance windows. Contacts are not billed and have no login.

    Best practices

    • Give every human their own login — don't share credentials.
    • Use the smallest set of roles that lets someone do their job.
    • Add an invoices@ contact so accounting always gets a copy.
    • Rotate API tokens every 90 days.