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 list and the form are on the Users screen; everything you do with one person is on that person's page.
The list
Administration → People → Users, tab People, shows everybody you manage: an administrator sees every person, a reseller the customers and customer members in its own realm.
- Search works on name, email address and customer name: search for "bakery" and you find the person who has access to Jansen Bakery.
- Filter on kind (customer, customer member, reseller, staff) and status (active, invited, disabled, locked). An administrator can also filter on realm. The filters are in the page's address, so you can send a filtered list as a link.
- The Access column says in one line what somebody can reach: the first customer and how many more, for example Jansen Bakery + 2.
- Last sign-in says never for somebody who has not used their invitation yet. On a tablet that column is left out; on a phone it is under More on the person's card.
Click a person to open that person's page.
Four kinds of user
Press Add a person. You first choose what kind of user it is; the form then asks only what that kind needs. A reseller is offered Customer and Customer member only.
| Kind | What it becomes | Who can create it |
|---|---|---|
| Customer | the owner of a new customer, with its company name and, if you use HostFact, the debtor number | an administrator; a reseller, inside its own realm |
| Customer member | somebody 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 date | an administrator; a reseller, for its own customers |
| Reseller | the operator of a new reseller realm, capped by a reseller package | an administrator only |
| Staff | an administrator or a server administrator; you give a server administrator their servers afterwards | an 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, at the top of the list as soon as the form has closed. After Dismiss it is gone. 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.comID TO KIND STATUS TRIES
3c9f1e70-a2b8-4d55-9e0b-6f2c1d9a4b8e jan@example.com person.invite sent 1person.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 — so pressing the button twice, or a slow network, never makes two. The form stays open and says the address already belongs to a person:
- If you chose Customer member, it offers Add the access to this person. That button gives the person the customer, role, accounts and end date you just filled in; no second login is made.
- For the other kinds it offers Open the person: you give an existing person that kind of access on that person's page.
If the address belongs to somebody outside what you manage, the form only says that the address cannot be used.
When something goes wrong, the message is in the form itself and everything you typed stays where it was.
The person page
Click a person in the list to open their page. At the top, next to the name, is their status:
| Status | Means |
|---|---|
| Active | has a password and can sign in |
| Invited | has not used the invitation yet, so has no password |
| Disabled | switched off; cannot sign in until enabled again |
| Locked | too many wrong passwords; the lock lifts by itself, or you unlock it |
Identity shows the email address, name, phone number, language, whether a second factor is on, and the last sign-in.
The buttons at the top are only the ones that apply now:
- Edit — name, email address, phone number and language. A new address is where the next invitation or link goes.
- Resend invitation — only while the person is invited.
- Send password link — once the person has a password (see below).
- Switch off or Switch back on — see below.
- Unlock — only while the person is locked.
Below that the page has four blocks:
- Customer access — per customer the role, every account or the chosen ones (2 accounts chosen), and the end date. Add access, Change and Revoke are on the block; see Giving somebody access. The owner's row has no buttons: a customer's owner changes by transferring the ownership.
- Servers — only for staff, and only an administrator sees it: which servers or server groups a server administrator has, and at which level. See Access to a server.
- Reseller realm — only for a reseller: the realm, the reseller package that caps it, and its customers and accounts against that package (18 of 25).
- Activity — the person's recent actions at their customers and the changes to their access. The audit log has everything; the block links there.
A reseller opens the page of the people in its own realm, without the Servers block. Sessions, the sign-in as this person, the data export and erasing work as before; erasing is refused while the person still owns a customer, and the refusal links to that customer's member list, where you transfer the ownership.
Switching somebody off
Switch off asks first, and then 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 password link asks first, and then 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