Onboarding, GitHub modes, and collaboration

1) Account onboarding

1. Create your Superprez workspace.
2. Open Settings from the sidebar.
3. Decide where new decks live: personal GitHub PAT (your repos, collaborator invites tied to GitHub identities) versus server-hosted (no GitHub) — drop-code saves the unzipped source in a per-deck folder on the Superprez server and tracks updates via local git commits.
4. Optional: add ChatGPT / Claude / Cursor credentials for in-app assistants.

2) Personal GitHub API token

Connecting your personal token lets Superprez create repositories on your behalf, wire webhooks, resolve collaborator emails against GitHub, download zipballs, and ingest collaborator or presenter zip uploads into main. You need this path for Add presentation → Connect repo and for Add presentation → Drop code when you toggle personal GitHub during upload.

Both Personal Access Token formats work — paste either in the same field:

• Fine-grained PAT (token starts with github_pat_) — recommended. Required permissions: Administration, Contents, Webhooks all read & write; Metadata read.
• Classic PAT (token starts with ghp_) — required scopes: repo + admin:repo_hook. Add read:org if the deck repo lives in an organisation.

Full walkthrough (both PAT types side-by-side, auto-update webhook, troubleshooting): Connecting GitHub.

3) Server-hosted decks (no GitHub)

The default for users without a personal PAT. Drop code saves the unzipped archive in a per-deck folder on the Superprez server (mounted from the named volume superprez_bundles), initialises it as a git repository, and points Superengine at a file:// URI for that folder. Subsequent updates rewrite the working tree and add a new commit on main; deletion removes the folder and its history. There is no GitHub repo, no remote push, and no webhook to register — collaboration happens through Superprez share links + the modification-zip panel on the deck page.

4) Drop code & ongoing zip updates

First-time drop-code either creates a private GitHub repository (if your personal PAT is connected) or a server-side bundle folder (otherwise). After that, owners of those decks see Update via zip (drop code) on the presentation page: upload a fresh archive to land a new snapshot commit on main and trigger check-for-update + update on Superengine. This works the same for both modes; the only difference is whether the commit is pushed to GitHub or recorded in the local server bundle.

See also: Drop code & zip updates (AI guide).

5) Collaborators without GitHub CLI

From Share, invite another Superprez user and enable Allow modification. They open the deck from Shared with me, download the source zip, edit with any AI or editor, and upload the replacement zip. Superprez commits on their behalf and refreshes Superengine—no local git required. Owners of drop-code decks get the same upload affordance for themselves.

6) AI provider keys

API keys for ChatGPT, Claude, and Cursor live in Settings for in-app generation. Building entirely offline in another tool is always fine: push to GitHub or use the zip round-trip described above.

7) Where to find the repository

• Hosted decks may hide raw owner/name plumbing—download zip from the dashboard if you need offline access.
• Personal or connected repos: open View on GitHub from Superprez (when surfaced).
• Search GitHub organizations linked to Superprez for repo names prefixed with your slug.