0.2.0 rebuilds access control around permissions. The built-in roles behave as before, so nothing changes for a team that only uses them.
One permission per action
Viewer, operator and admin are now fixed sets drawn from one permission vocabulary. Every environment route checks the single permission it needs. Applying multi-document YAML checks each document before any is sent, so a batch never half-applies because of a missing grant.
Reading a Secret’s value is its own permission, reveal. Admins have it. Helm plans hide values from anyone without it.
The web UI follows the same rules: it shows only the actions your role allows, instead of offering a button that fails.
Custom roles and teams (Enterprise)
Roles lets an admin build a role from the permission list, for example an operator who can restart and read logs but not open a terminal. Changes to a role take effect at once for everyone who holds it, and are written to the audit log.
Teams grant access to a group of users at once. A user’s dialog shows their effective access on each environment and where each grant comes from: directly, or through which team.
Without a license, existing roles and teams keep working but are frozen; you can still remove them.
Licenses count nodes
Enterprise licenses now carry a node limit instead of a user limit, matching how pricing works. Users are never limited. The License page shows the current license and accepts a new .lic file.
Next
Single sign-on, LDAP and scheduled backups are merged and will ship in the next release. See the roadmap.