Sign in with Google, or have a one-time link emailed to you — either works, and both reach the same account. The email carries a code as well as a link, for when you are reading it on your phone and signing in on a different computer. Access is given by an administrator; if you cannot get in, ask your bishopric.
or
Scan this with an authenticator app — Google Authenticator, Microsoft Authenticator, 1Password, Authy. Then type the six-digit code it shows.
Cannot scan it? Type this key into the app by hand:
— bulletins and ward details do not need a code. Cannot get one at all?
One row per bulletin per day, counting devices, not people.
A device is a random token the browser keeps to itself, hashed with the date
before it is sent — so two days cannot be matched up and nobody is
identified. A phone and a laptop are two; a private window each time is a
new one every time. Days are Central Time.
First time is the browser's own answer to “had I been
here before today?”, sent as a single bit. It says whether readership is
the same people coming back or new ones arriving, without the site ever
holding anything that could follow somebody. A cleared browser reports itself
as new, so read it as a shape rather than a count.
No stake programs yet.
One program covers a whole weekend. Each meeting inside it is a session, with its own officers and its own order of business.
Nothing has been saved yet. Check it over, then create it — everything here can still be edited afterwards.