Inviting your team and roles overview

Humavera is built to be run by more than one person, with each teammate seeing and doing exactly what their role allows. This article explains how access works conceptually.

Admins and members

At the broadest level, there are administrators and members. Administrators configure the platform, manage people and settings, and control who can do what. Members work within the permissions they are given — using the tools relevant to their role without access to everything around it.

Role-based access, configurable to your org

Access in Humavera is role-based. Rather than a fixed set of tiers, permissions are configurable, so you can shape roles to match how your organization is actually structured — who can see compensation, who can approve workflows, who can run payroll, and so on.

Least access by default

The safe principle is to grant each role the minimum it needs. Because permissions are granular, you can start narrow and widen access deliberately rather than opening everything and clawing it back.