Your team and account security
Invite colleagues, choose their role, turn on a second step and manage API keys.
Roles
| Role | Can do |
|---|---|
| Owner | everything: team, billing, security settings, API keys, rotate keys, close the account |
| Billing | payments, quotes and renewals; sees licenses and devices; cannot manage the team |
| Viewer | read-only: sees licenses, devices and downloads |
An account always has at least one owner. To hand over ownership, an owner chooses another member under Team and confirms with their password.
Invite someone
Under Team, enter their email and a role. They get a link that works once and expires after a short time; you can resend or revoke it while it is pending. They choose their own password. Removing a person signs them out and tells them by email.
Second step at sign-in
Everyone should add an authenticator app under Security. An owner can require it for the whole account; people who have not set it up are asked to the next time they sign in. Keep the recovery codes somewhere safe: each works once, and they are the way back in if the phone is lost. If an owner is locked out and has no recovery code, contact us; we will verify who you are before doing anything.
API keys
Owners can create read-only API keys under API keys to list licenses and devices from scripts. A key is shown once when it is created or rotated; we keep only a fingerprint, so a lost key must be replaced, not recovered. Give each key a name that says where it is used so you can revoke the right one.
What we do to protect your account
Passwords are checked against common and breached passwords and cannot contain your name or email. After repeated wrong passwords, sign-in waits before accepting more attempts. You are emailed when a password changes, when someone signs in from a browser we have not seen, and when a recovery code is used. Our support team can look at a read-only view of your account only with a written reason, and you are emailed each time; see using your account.