Accounts

Sign in with Google or GitHub

Choose Google or GitHub on the sign-in page. Your first successful sign-in creates an account automatically. There is no separate registration form, email/password login, or password recovery.

Use an account with a verified email address. If you use both providers, they must supply the same verified email address to link to the same ShortDramaKit account.

Manage a profile

Signed-in users can update their display name in account settings and sign out. The current profile form does not change the email address or grant administrator access.

The server accepts only the supported fields. It does not trust role fields supplied during sign-in or profile updates. Session responses expose the public account fields, not password hashes or OAuth provider tokens.

Configure sign-in providers

Create dedicated Google and GitHub OAuth clients for the application you are building and configure their credentials in secret storage. Do not reuse another application's clients or commit secrets.

Register these callback paths against the deployed HTTPS application origin:

The application offers a provider only when its required configuration is present. A successful synthetic OAuth test does not establish that a real OAuth client, consent screen, or callback domain is ready. Verify the real browser sign-in after configuration.

Separate administrator access

Administrator access comes from a controlled operator update to a known user's D1 record. It cannot be requested through public sign-in or settings forms. The administrator view reads real users and orders and does not include a browser control for granting roles.

Authority is read from the database on each protected request. Revoking an administrator role therefore takes effect for an existing session without requiring that user to sign in again.

Return to Getting started, or see API access for server-side keys.