A person requesting access or a commissioner reviewing admission.
Anonymous/authenticated states; pending appears only when an implemented admission capability exists.
HELP TOPIC // getting-started
/identity-admission-and-membership · corpus 0.1 · verified 43c1c50
Identity, admission, and membership
Separate person, sign-in, league admission, and team association.
Sources
Who can use this answer.
Read the current gate
Use the intended identity. Admission is evaluated before team association.
The label carries the consequence.
Not-admitted, pending, admitted seatless, associated, and denied are distinct.
Use the runtime clock
Configured admission/expiry policy is rendered in league-local time.
Keep the right audience
Authentication proves the requester; public help does not disclose admitted identities.
Take the next safe step.
- →
Sign in with the intended account.
- →
Read the rendered admission reason.
- →
Claim or confirm a team only when eligible.
- →
Ask the commissioner to correct a wrong invite or assignment.
Know what changes.
What happens
A signed-in person is not automatically a member, and an admitted member may remain seatless.
What can be undone
Wrong association follows the audited commissioner path; aliases may not bypass policy.
What you should see
The page reports persisted admission/association and the valid next action.
Keep context. Do not replay blindly.
Rejected or malformed auth returns safely with no membership mutation.
Use the displayed access route or /guide#identity; do not reauthenticate when the issue is admission.
One concrete read.
Example: An unadmitted identity sees its reason and request route, not a misleading claim form.
Runtime source: OAuth identity, membership policy, aliases, membership rows, and team associations.
Corpus receipt: introduced 0.1; last verified 43c1c50dfbd493b01368d2c74959eb23de098749.