The first profile is always admin
There’s no separate setup account — whoever creates the install’s first profile can manage everything.
Add more profiles as needed
From Settings → Manage Profiles (admin only), picking a role for each.
Lock a profile, optionally
Add a password from Settings → Profile — switching to that profile then asks for it.
Roles
Every profile is either an admin or a reader:
- Admins can create and delete profiles, assign roles, delete recipes, and edit the server-wide library settings (pagination, search result limit, upload size limit)
- Readers can only edit their own profile (name, color, password)
Recipery won’t let you delete the only profile on an install, or the only remaining admin — there’s always at least one profile, and it’s always able to manage the place.
What’s per-profile
Each profile keeps its own:
- Name and color
- Collections (see Collections)
- Ratings, favorites, and cooked status for every recipe
- Password lock
The recipe library itself is shared — every profile sees the same recipes, just with its own collections and cooking state layered on top.
Password protection
A profile’s password is optional and locks switching into that profile, not the whole install. Passwords are hashed with salted scrypt on the server; the hash never reaches the client, and a profile with no password set is never locked.