Contents
Start here
TERSL — the language
TERSL/DB — the system
Portal guide
HTTP API
Reference
Portal guide

Users

The Users pages are where an administrator invites people to the account, sets their role, gives them keys and logs, and deactivates or deletes them.

What this page is for#

The Users page (/users) lists the people who can sign in to the account and is where an administrator adds new ones. Each person's own page (/users/{id}) sets their role, the keys they may use and the logs they may read, and holds the account actions: unlock, a new sign-in link, deactivate, reactivate and delete. The page also holds the workspace's two-factor requirement.

Who can see it#

Administrators only. A limited user who opens either page gets a 404.

The two roles differ as follows. An administrator can do everything, including adding users and keys, editing grants, managing billing and reading every log. A limited user can use only the keys they were given, in the Explorer and the other pages that act through a key, and read only the logs they were given; they cannot add, revoke or rename a key, and the Grants, Users and billing pages are refused to them. Reading a log gives no access to a key, and holding a key gives no access to its namespace's log.

What is on the page#

Seats#

The line "2 of 10 seats in use." counts active users against the plan's seat limit. Deactivated users do not occupy a seat. When every seat is taken, the add button is disabled with the caption "Your plan allows N seats."

Sign-in policy#

The Sign-in policy panel shows "Require two-factor sign-in for everyone:" followed by on or off, and a Turn on or Turn off button. The requirement applies to everybody in the workspace, including people who are already signed in; they are asked to set it up on their next page. If you have not turned on two-factor sign-in for your own account, the panel asks you to do that first and links to your account. If the deployment cannot send sign-in codes, the panel says "This deployment cannot send sign-in codes yet."

The user table#

The table has the columns Email (with administrator and you chips), Status (Active or Deactivated), Created, Sign-in ("password set" or "invited — link not used yet"), Last sign-in (with a "locked until" chip while an account is locked out), Keys and Logs. The last two count what a limited user was given and are empty for administrators, who have everything. Click an email to open that person's page. Type in Filter by email to narrow the rows.

A person's page#

The page heading is the person's email, with their status, "administrator" if they are one, "invited — their link has not been used yet" if they have not signed in, and "this is you" on your own page. It has four panels:

  • Administrator, with the button Make an administrator or Make a limited user.
  • Keys they may use, a checkbox per key with its label, status and, for keys the person holds, where the key is granted. Save keys applies the change.
  • Logs they may read, a checkbox per namespace. Save logs applies the change.
  • Account, with the actions described below.

Actions#

Add a user#

Press Add user. In the flyout, type an Email, tick Administrator if the person should be one, and, for a limited user, tick the Keys they may use and Logs they may read. Press Add.

Adding a user produces a one-time sign-in link. The portal emails it, and the page says "Invited - a link was sent to address. It is good for 72 hours." On a deployment that does not send email, the page shows the link once instead, under "Give this link to address now. It will never be shown again.", with a Copy button. The person opens the link, chooses a password and signs in. The link works once.

Change a user's role#

On the person's page, press Make an administrator. The page asks "Make address an administrator? They can do everything, including adding users and keys, from their next page." Press the button again to confirm. Make a limited user asks "Make address a limited user? They keep the keys and logs they were given and lose everything else, from their next page." The keys and logs lists are kept while someone is an administrator, so they apply again if the person is made a limited user.

Give or take keys and logs#

Tick or untick keys under Keys they may use and press Save keys; do the same under Logs they may read and press Save logs. The change applies from the person's next page. A key a person holds still reaches only what each namespace's grants allow it.

Unlock#

While an account is locked after too many failed sign-ins, the Account panel shows "Locked until" a time and an Unlock button. Unlocking clears the lockout and the failed-attempt count; the password does not change.

For someone who has not used their invitation, the button is Resend invite; for someone with a password it is Send a reset link. The page asks for confirmation: "Make a new invitation link for address? The link they have now stops working." or "Make a new link for address? Every session they have is signed out and their old link stops working." The confirmation also offers Show link once, which displays the new link on the page instead of emailing it. On a deployment that does not send email, the buttons are Re-issue invite link and Reset password (new link), and the link is always shown once. A new link works once and stops working after 72 hours.

Deactivate and reactivate#

Deactivate asks "Deactivate address? They are signed out and cannot sign in until reactivated. Their permissions are kept." A deactivated user frees a seat. Reactivate lets them sign in again and take a seat, with their permissions as they were.

Delete#

Delete asks "Delete address?" and explains "Their permissions go with them. Nothing they were given access to is touched: no key is revoked and no namespace is removed." Press Yes, delete. The last active administrator cannot be deleted.

Turn the two-factor requirement on or off#

In Sign-in policy, press Turn on. The page asks "Require two-factor sign-in for everyone? Everybody in this workspace, including people signed in now, is asked to set it up on their next page." Confirm with Turn on. Turn off asks "Stop requiring two-factor sign-in for everyone? People who set it up keep it; nobody else is asked."