Roles control what each person on your team can see and do in InfraNest. This article is for anyone who manages team members or wants to understand what their own role allows.
Overview
- InfraNest comes with built-in roles for common needs, and you can create your own for anything more specific.
- Each role is built from a set of permissions covering areas like cloud resources, DNS, domains, monitoring, certificates, members, billing and roles.
- What you can give others depends on what you yourself have access to.
Built-in roles
InfraNest includes three roles that are shared across your organization and can't be deleted:
- Owner — full control of the organization.
- Admin — can manage resources and members.
- Member — day-to-day access for regular work.
Create a custom role
If the built-in roles don't fit, you can build your own from a permission matrix.
- Go to Roles and select Create role (or New role).
- Give it a name in Role name. You can't use Owner, Admin or Member — those are reserved for the built-in roles.
- Tick the permissions it should have, such as View servers & cloud resources, Create & manage cloud resources, View DNS zones & records, Edit DNS zones & records, View domains, Create & edit domains, View monitoring checks, Create & manage monitors, Manage members & invitations, Manage billing, or Create & manage custom roles.
- Select Save role, then assign the role to a team member.
NoteNobody can hand out more access than they have. You can only give someone a role whose permissions you also hold, and you can only change or remove someone whose role doesn't go beyond your own. Owners can assign any role — so, for example, an Admin who can't manage billing or roles can't create or assign a role that can.
What someone sees without a permission
InfraNest only shows what a person's role allows:
- If someone can view something but not change it, the buttons to add, edit or delete it are hidden.
- A short note at the top of the page explains that the page is read-only for them, and names who in the organization can make changes (owners first, then people who manage members).
- Opening a create or edit page directly shows the same explanation instead of a form.
Settings pages follow the same rule: members, roles and sign-in settings need Manage members & invitations; billing tabs need Manage billing.
NoteThe full, always-up-to-date list of roles and permissions is available to admins in your settings.
Was this article helpful?