Documentation
This is the complete catalogue of what you can grant. Everything Everlock controls is reachable through **one** grant model: a `role` attached to a subject (user or group) on an `access path`. There i
Everlock uses a path-based grant system to control who can read from and push to repositories. Every access decision — clone, push, admin action — is checked against a table of grants attached to user
By default, every site Everlock creates is public: anyone who can reach the server over HTTP can read the pages. Public access is expressed through the built-in `anon` user having `Reader` on `http/si
Everlock has a single unified user model shared across all frontends and backends. The same user identity that authenticates over SSH to push a Git repository is also the one that authenticates to an
All user management happens from the admin SSH console. This page covers creating users, managing passwords, listing users, and the two special access rules that apply automatically without any explic
