Status and security
Roles, network limits and API tokens
Give people only the access they need, require two-step verification, limit the networks that can reach the console and create read-only API tokens.
Steps
Know the built-in roles
There are five: owner, reseller administrator, tenant administrator, supervisor and agent. What each may do is enforced on the server for every request. The console only uses the same list to decide what to show.
Make a custom role
Open Roles and choose Make a role. Give it a name, a Base role (agent or supervisor) and the capabilities it needs, then choose Make the role. A role applies from the holder's next request, and every change is in the audit log.
Assign it
Under Who holds which role, choose a role for each person. Some capabilities stay with tenant administrators alone, and the page lists them.
Require two-step verification
Open Security. Under Organisation policy, tick Every user must use two-step verification and choose Save policy. Everyone then sets it up: see Set up two-step verification.
Limit the networks
In the same policy, list the networks allowed to use the console and the networks allowed to use API tokens, one CIDR block per line. An empty list allows all. A console list must include your current address, or it is refused so that you cannot lock yourself out.
Create an API token
Under API tokens, enter a name and the number of days it is valid for, and choose Create token. Copy the token straight away: it is not shown again. A token reads your organisation's data and cannot change anything. Choose Revoke to stop one.
Good to know
- Organisations that use their own identity provider can set up Single sign-on.
- Report a security problem to security@ringura.com.
Still stuck?
Write to hello@ringura.com, or use the contact page, and say which guide you were following.