Team and access

Roles

Role	Can
Owner	Everything, including who is owner.
Admin	Add sites, change settings and manage the team.
Editor	See all numbers, plus manage goals, funnels and labels.
Reader	See all numbers; changes nothing.

An organisation always has at least one owner. Only an owner can make someone owner or change an owner.

Manage roles in the user menu (top right) › Team (/app/team): choose the role per person, remove someone, or leave yourself. API: GET /v1/orgs/{org}/team, PATCH and DELETE /v1/orgs/{org}/members/{user}.

Invite someone

Team › Invite someone: an email address and a role, for all sites (including new ones) or for some sites.

• As soon as that person signs in to nvivio.com with exactly that address, the access is there. Nobody needs a password or an account made for them.
• An invitation expires after 30 days and cannot be used by anyone else.
• The invitee gets an email from Nvivio, in the language of the person who invites: who invited them, for which organisation or sites, with which role, until when, and a button to sign in.
• You can also copy a ready-made message to send yourself.
• Open invitations can be withdrawn.
• Limits: up to 30 invitation emails per organisation per day, and up to 50 open invitations.

API: POST /v1/orgs/{org}/invitations with email, role and optionally sites (the answer says in emailed whether the email went out); DELETE /v1/orgs/{org}/invitations/{id}.

Access to one site

Give a client or freelancer access to one site, as admin, editor or reader, without them seeing the rest of your organisation: other sites do not exist for them, and they see your team only as a number. The admin of such a site can invite people for that site, never for the organisation. Someone who leaves the organisation also loses this access.

Use the site’s Settings › Access (/app/<your-domain>/settings#access), or Team › Invite someone › Only these sites. API: GET and POST /v1/sites/{site}/access, PATCH and DELETE /v1/sites/{site}/access/{user}, DELETE /v1/sites/{site}/invitations/{id}.

Built to be safe

• Every rule is checked on the server, not on the screen.
• A team is only managed by a signed-in person, never with an API key, so a leaked key cannot hand out access.
• Without a role you get “not found”, so you do not even learn that a site or organisation exists.
• The tables are locked in the database like everything else: no access through the public database API, and row-level security on.
• Tests try every way of raising rights and require that they fail.