@@PRODUCT@@

Managing users

A user is a person who can sign in to the panel. Every person has one email address, one password and their own second factor — however many customers they work for. What they may do comes from the access you give them.

Written for: Administrator, Reseller

A user is a person who can sign in to the panel. Every person has one email address, one password and their own second factor — however many customers they work for. What they may do comes from the access you give them.

The Users screen gets the new form and the person page in one of the next releases. Until then everything below is available through the panel API (POST /api/v1/persons and the routes beside it, see the API reference), and the existing screen keeps working as before.

Four kinds of user

When you create a user you first choose what kind of user it is. The rest of the form follows from that choice.

KindWhat it becomesWho can create it
Customerthe owner of a new customer, with its company name and, if you use HostFact, the debtor numberan administrator; a reseller, inside its own realm
Customer membersomebody who works for an existing customer, with a profile (full, technical, mail, DNS or read-only), for all of the customer's hosting accounts or only some, optionally until a datean administrator; a reseller, for its own customers
Resellerthe operator of a new reseller realm, capped by a reseller packagean administrator only
Staffan administrator or a server administrator; you give a server administrator their servers afterwardsan administrator only

Name, email address, language (Dutch or English) and an optional phone number are the same for every kind. Billing and address details stay in HostFact.

The password

You choose one of two:

  • Let the user set it (the default). The user gets an email with a link to choose their own password. The link works for seven days and once. Until they use it the user reads invited. Lost the mail? Send the invitation again: the new link replaces the old one.
  • Generate one. You see the password once, on the screen where you created the user. Hand it over another way than email. It is not stored anywhere you can read it back, and not in any log.

Did the invitation arrive?

On the panel server you can see whether the mail left, without opening it:

corecp-panel mail queue --to jan@example.com
ID                                    TO                 KIND           STATUS  TRIES
3c9f1e70-a2b8-4d55-9e0b-6f2c1d9a4b8e  jan@example.com    person.invite  sent    1

person.password_reset is the kind of a reset link. The link itself is never shown there: it is in the user's mailbox and nowhere else.

An address that already exists

One address is one person. If you create a user for an address that already belongs to somebody you manage, nothing new is made and you are pointed at that person — so pressing the button twice, or a slow network, never makes two. If the address belongs to somebody outside what you manage, you are only told that the address cannot be used.

Switching somebody off

Disable stops a user at once: every session they have ends straight away — an open terminal and notifications included, and a support session somebody holds as them — and they cannot sign in until you enable them again. Nothing of theirs is removed.

The owner of a customer cannot be disabled; transfer the ownership to somebody else first (see Giving somebody access). You cannot disable yourself.

A new password

Send a password-reset link mails the user a link that works for one hour and once; a newer link replaces an older one. If the user has two-step verification, the panel still asks for their code after the new password. The answer is the same whether or not the address belongs to anybody, so nobody can use it to find out who has an account.

Confirming who you are

Creating a user, changing somebody's email address and sending them a link ask you to confirm who you are if you have not done so in the last ten minutes. That is deliberate: these are the steps somebody would take to get into another person's account.

See also

  • Giving somebody access
  • Access to a server