Administration
People, sign-in and API keys
Who can do what in your organisation, how people sign in, and how to use API keys.
Roles
| Role | What it may do |
|---|---|
| Viewer | See work, projects, engineers and requirements. Change nothing. |
| Member | Everything a viewer may do, and hand over work, create requirements and approve them. |
| Admin | Everything a member may do, and manage connections, engineers, people, API keys and billing. |
For the admins of your organisation.
Inviting people
Admins invite people from People, billing, activity. If your organisation limits sign-in to its own e-mail domains, invitations to other domains are refused.
API keys
An API key lets a program act for your organisation, with the role you give it. The key is shown once when it is created; Yavaren keeps only a fingerprint of it. Revoke a key you no longer use.
The activity log
Every change in your organisation is recorded: who, what and when, including attempts that were refused.