Skip to content
Explore features

Accounts and access, with clear boundaries.

Explore personal account settings, local project permissions and member access. Each path opens an existing browser example for that task.

Explore account paths

Page editing is unavailable in this context. Your saved text is kept.

Clear account paths. Explicit access.

Personal account settings, local project permissions and customer membership serve different jobs. Explore each path in the existing browser examples.

Browser examples only. No real account or service is connected. Kottoko organization accounts and deployed-project accounts are distinct.

Read-only guide

Manage a personal account

Read-only guide to the existing project-local account examples. Selecting a path does not sign you in.

  1. Verification follows the saved email

    Save an invented profile, inspect verification and recover from a failed sample check. Changing the saved email requires a new check.

  2. Choose supported account protection

    Inspect authenticator confirmation and passkey availability. A real account needs recent identity confirmation and compatible features and devices.

  3. Keep recovery private

    Inspect the recovery explanation without generating codes. Real recovery codes are private; replacing them invalidates the previous set.

  4. Review current and other sessions

    Inspect sample sessions and confirm removal of another sample session. The current sample stays active.

  5. Keep personal choices separate

    Try saved and unsaved communication choices. Sample appearance does not change project design; website language and browser consent remain separate.

  6. Review export and removal

    Preview saved sample data and a cancellable removal request. Owner safeguards and retained-record explanations remain visible.

How sign-in and recovery work

Installed Accounts supports registration, email verification, sign-in and password reset. Follow that project’s recovery flow if you cannot sign in. This public guide asks for no password, sends no email and does not authenticate you.

The examples are unavailable while this browser draft is loading or blocked. Your saved choices are kept.

The member destination is unavailable in this context. No account or access changes.

When access needs attention

A denied permission and an expired session need different recovery. In a real project, sign in again for an expired session, or ask its authorized owner about access. A verification failure does not grant more rights.

Organization access is separate

Kottoko organization roles, Creator seats and commercial entitlements are distinct from local project permissions and customer membership.

An organization role describes a responsibility. Creator-seat assignment is separate; payment alone does not assign a role or local permission. Billing access does not imply source access.

A deployed project controls its own users, content and access. Production content, submissions, secrets and local user directories are not synchronized to the organization service. There is no hidden support account.

Keep each kind of access separate

Your deployed project manages its own accounts and permissions. Member access protects its resources. Kottoko organization roles and Creator seats are separate from both.

Explore Settings