Who this is for: administrators inviting their team, and anyone wondering why they can or cannot do something.
Access is by invitation only. To ask about access for your organisation, use the form at nebli.ai/environment.
Invitations
Nobody signs up alone. An administrator invites each person from Settings › People, giving their name, their email address, the language of the invitation email, and a role. An invitation is for one organisation.
- The role is chosen by whoever invites, and it can never be higher than their own. The form starts at Viewer.
- A role is fixed once the invitation is sent. To change it, revoke the invitation and invite the person again.
- The invitation email names your organisation and the product's address. It carries no link and no code. The person goes to env.nebli.ai and signs in with the invited email address, and that claims the invitation.
- An invitation stands until it is claimed, revoked or expires, even if the person who sent it later leaves. Pending invitations, and when each one expires, are listed in Settings › People, where an administrator can revoke them.
- A person cannot change their own name; an administrator can, from Settings › People.
Signing in
There are no passwords. Each person signs in with a code sent to their email:
- Go to env.nebli.ai, enter your work email and choose Send code.
- Type the eight-character code from the email, shown as XXXX-XXXX, in any case and with or without the dash.
The code works once, for a few minutes, in the browser that asked for it. A mistyped code does not lock you out. An email address that is not in any organisation sees the same screen, so the sign-in page never reveals who has an account.
Signing out ends your session everywhere, not only in the browser you are using. Sessions also expire on their own, after a period of inactivity and after a fixed lifetime.
What each role can do
Every person who is signed in can see the map, the nodes and their pages, the table and the network page. Beyond that, each role adds to the one before it.
| Role | Can also |
|---|---|
| Viewer | See alerts and rules. |
| Analyst | Export: the table as CSV, and the raw readings. |
| Operator | Acknowledge and close alerts. |
| Engineer | The same as an operator today. The engineer role is meant for the person who keeps the sensors running; it carries the operator's rights. |
| Administrator | Create and change alert rules; manage nodes (import, assign to a site, rename, move, retire, restore, and replace hardware); and everything in Settings: people and invitations, the organisation, sites, adapters and their credentials, API keys, delivery targets and retention. |
Anything a role is not given is refused.
Language
Each person chooses English or Spanish. It starts as their browser's language and can be changed at any time from their menu or from Settings.