⚠ This page's script did not run, so nothing below is live — including this
banner, which is static text. Open the browser console (⌥⌘I / F12) and look
for a syntax error. If you edited the file by hand, that edit is the first
place to look.
Brooklyn Debate League
Account Manager
Checking your session…
Script did not run — this line is static text.
Brooklyn Debate League
Account Manager
—
Waiting for a decision
Request
Select a request to review it.
This is a list of account requests, not a list of people with
logins. A login bound some other way has no request row and
will not appear here — its absence is not evidence that nobody is
bound. Schema 153 names three paths by which that happens, and one of
them closes under BDL-312; this page does not try to count them.
Unbinding clears the link and turns the account away at sign-in; the person is not deleted and the original binding stays in the log.
Changing somebody's role after they are bound — including making them an Admin — happens on the Roles tab. Binding itself grants one function role at creation and nothing after.
Unbinding clears the link and turns the account away at sign-in; the person is not deleted and the original binding stays in the log.
Changing somebody's role after they are bound — including making them an Admin — happens on the Roles tab. Binding itself grants one function role at creation and nothing after.
Account requests that were bound
| Account | Person | Bound | Signed in | Action |
|---|
Roles are dated. Granting one starts it today; ending one sets a last
day, and that day counts — a role ended today stays
active for the rest of today. Nothing is deleted: an ended role stays
in the person's history.
Find a person
Roles
Select a person to see what they hold.
Most people on a roster have no account, and that is the
normal state.
An account is how somebody signs in to this site. Students are
overwhelmingly minors, and a minor having no login is not a gap to
close — it is the ordinary case. This list is for finding the person
who asked for an account and never got one, not for chasing
everybody who has not got one.
Ruling 48.4: only people who actually have an account are named here; everybody else on the roster is counted and left unnamed. Registry 5.2: sign-in shows as yes or not-yet for everyone, minor or adult — this tab never shows a sign-in time.
Nothing here grants, binds or changes anything. It is a list.
Ruling 48.4: only people who actually have an account are named here; everybody else on the roster is counted and left unnamed. Registry 5.2: sign-in shows as yes or not-yet for everyone, minor or adult — this tab never shows a sign-in time.
Nothing here grants, binds or changes anything. It is a list.
You are seeing all of this roster or none of it. The
gate on a roster read is all-or-nothing, so there is no partial list
and no hidden remainder — if you can see a roster at all, this is the
whole of it.
Roster
| Person | Account | Age | Signed in |
|---|
An unknown age counts as a minor, everywhere.
No date of birth is collected when an account is requested, so a person
is treated as a minor until an administrator attests otherwise. That
default is the safe one, but it only holds while somebody works this
list — a pile of unattested adults looks exactly like a population of
children, and the failure mode is silence.
Everyone here holds a login, has no date of birth on file, and has no attestation standing. Attesting is reversible and both directions are logged — but a wrong attestation strips a child of every protection in the meantime, so leave anyone you are unsure of exactly where they are.
Everyone here holds a login, has no date of birth on file, and has no attestation standing. Attesting is reversible and both directions are logged — but a wrong attestation strips a child of every protection in the meantime, so leave anyone you are unsure of exactly where they are.
Bound people with no age settled
| Person | Account | Bound | Programme | Action |
|---|
Denied requests
| Account | State | Requested | Resolved | Action |
|---|
Every action is appended here with the administrator who took it. Binding
a login to a person is identity assignment — this is the record of who
assigned whose. Append-only: no administrator can edit or delete a row.
People appear as ids, not names. The log carries no foreign keys on purpose, so that purging a request cannot be blocked by its log rows — the cost is that this table is precise and hard to read. A view joining display names would fix it; asked for.
People appear as ids, not names. The log carries no foreign keys on purpose, so that purging a request cannot be blocked by its log rows — the cost is that this table is precise and hard to read. A view joining display names would fix it; asked for.
Activity
| When | Administrator | Action | Subject | Reason |
|---|