Until now the sign-in behind the private area was a single allow-list in configuration: to let someone in, the owner edited a setting and redeployed. The owner asked for something they could do from the site itself, and for a way to make other admins when the time came.
Two roles
There are now admins and members. Admins see a Users page under the private area and an API behind it; members see everything else and no Users link. The first admins are seeded from the same configuration list that used to be the whole allow-list, so nothing had to be migrated by hand.
Signed out once
The session cookie had to start carrying who the session belongs to, which meant a new cookie version. Every existing session was invalid the moment it deployed, and everyone signed in again. A one-time cost, taken on purpose rather than keeping two cookie formats alive.
Merged by the owner
This was Factory job 009 for the site. It touched the Worker, which is on the guarded list, so the pipeline stopped at the end and waited. The owner read it and merged it by hand; the deploy waited on the owner too.