Roles
Roles
lazyit ships with three fixed roles: Admin, Member and Viewer. Every user has exactly one. You cannot create, rename or delete roles — the set is the same on every install, which keeps the model small and predictable for a small IT team.
A role is the access level a person holds. What that level actually lets them do is decided by permissions (see Permissions), and for Member and Viewer those permissions can be tuned. The role is the thing a user has; permissions are what a role grants.
The three roles
- Admin — full control of the instance. An admin can do everything: manage users and their roles, change instance settings, delete records, grant and revoke application access, and adjust what Member and Viewer may do. Admin always holds every permission and that set is never editable — this guarantees the instance is always operable by someone with full power.
- Member — the everyday working role. By default a Member can read and create/edit most things (assets, applications, consumables, the Knowledge Base, locations, models, categories) but cannot delete records or perform admin-only actions. A Member can also use the AI assistant and connect external AI agents, once an administrator turns them on — always with the Member’s own permissions.
- Viewer — read-only. By default a Viewer can look at most areas but change nothing. A few sensitive views (the user directory, the access-grant ledger, and purchases and suppliers) are also hidden from Viewer by default.
The Roles & permissions page
Settings → Roles & permissions is one matrix: what each role can do, with Admin as a locked
reference column beside the editable Member and Viewer columns. Each column header shows a live
holder count (how many active users currently hold that role); click it to open the
Users list filtered to that role — the Users list is where you
actually browse and manage who holds it, with search, sort and paging. Editing what Member and Viewer
may do is described in Permission configuration.
(The old address of the per-role editor, /settings/roles/permissions, now opens this page.)
How a role is assigned
- The first user is always Admin. The very first person provisioned on a fresh install — whether through the setup wizard or the first sign-in — becomes Admin, so a new instance is never left without an administrator.
- Everyone after that starts as Viewer. Newly provisioned users default to the least-privileged role (read-only) until an admin promotes them. This is deliberate: a new identity can look but not change anything until someone grants more.
- Admins change roles from the Users section. Open a user (or use the role cell in the Users list) and pick Admin, Member or Viewer. lazyit asks you to confirm the change.
Built-in safety rules
These guardrails protect the instance from being locked out or quietly escalated:
- The last admin cannot be removed. lazyit refuses to demote, deactivate or offboard the final remaining admin — there must always be at least one. You will see a clear message instead of the change going through. Only admins who can actually sign in count: an admin who has never signed in through your identity provider, an admin without a password on a local-accounts install, or a directory person does not keep the instance administrable.
- Nobody manages users above their own role. If you give Member or Viewer the Manage users capability, those people can only hand out their own role or a lower one, and can only edit, reset, offboard or restore users whose role is at or below theirs. Only an admin can create an admin, promote someone to admin, or act on an existing admin. The role pickers only list the roles you can hand out, and on a user above your role the role shows as a plain badge and Edit, the password reset and Offboard are not offered (cloning them still is). Anything else is refused with a clear message.
- Only an admin edits permissions, the directory connection and the email settings. Giving Member or Viewer Change instance settings lets them view the permission matrix, the directory connection and the email (SMTP) settings, not change them or run a directory sync. The service accounts they manage can hold only permissions their own role has.
- Promoting someone cancels their pending sign-in credentials. When a person’s role goes up, a temporary password they have not replaced yet and any password-reset link still waiting are cancelled, so one handed out at the lower role stops working. The role-change confirmation warns you first, and the success message reminds you. If they need one, issue a new temporary password or reset link after the promotion.
- You cannot change your own role. An admin cannot promote or demote themselves; a role change must be made by one admin on another. This prevents a single person quietly elevating their own access. (You can still edit your own name, email and other details.)
- A directory person’s role cannot change. People added by an import or the directory sync have no login and stay Viewer until they are onboarded. Their role shows as locked, with the reason; onboard them first, then change the role.
A note on your identity provider
Roles are managed locally in lazyit, whichever way people sign in. With your own OIDC provider they are not read from a token and are never sent to the provider; they are used only for authorization inside the app. You assign and change them here, in the Users section.
For the full breakdown of what each role can do — and how to tune Member and Viewer — see Permissions and Permission configuration.