Основы аккаунта, организации и сессии
This guide separates аккаунт identity, organization membership, current session, and active organization context so readers know where they stand before integration or организация-scoped actions.
Registration is invitation-led
Current registration requires an invitation token; документация must not describe open registration as available.
Account, membership, and session are different
аккаунт says who you are, membership says which organization you belong to, and session says whether you are currently signed in.
Read the current state after sign-in
After sign-in, first read аккаунт, membership, session, active organization context, and access boundaries.
When active organization context is required
Before организация-scoped actions, the user must confirm which organization they are acting for.
Session management handles sign-in state
Session refresh and revoke handle current sign-in state; they do not change organization membership or administrator responsibility.
Continue reading
Continue to organization invitation acceptance and onboarding after identity and организация context are clear.