Onboarding, GitHub modes, and collaboration

1) Account onboarding

1. Create your Superprez workspace.
2. Open Settings from the sidebar.
3. Decide where new decks' Git source lives: personal GitHub (your repos + collaborator invites tied to GitHub) versus Superprez-managed GitHub when you upload a zip—the workspace provisions private repositories on GitHub using operator-configured access so Superprez can git clone over HTTPS (there is no on-disk bundle folder on Superprez for deck source).
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 → Upload when you choose My personal GitHub.

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) Superprez-managed GitHub (zip uploads)

When you upload a zip and choose Superprez GitHub (or equivalent default), Superprez creates a new private GitHub repository using workspace-wide access configured by your operator, imports your archive via GitHub's APIs, and installs the deck from https://github.com/… like any other repo. Updates rewrite the repo contents with new commits; deleting the presentation can delete that GitHub repository. You still rely on GitHub's infrastructure—which means Superprez legal notices include disclosure about GitHub's terms when you use this path without your own linked account.

The product UI intentionally avoids surfacing raw org/bot URLs for Superprez-managed repos; use zip download/share flows when you need a portable copy.

4) Drop code & ongoing zip updates

First-time Upload creates a private GitHub repo either under your account (personal PAT path) or under Superprez-managed hosting (operator PAT/org path). Owners then 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 Superprez. Both modes talk to GitHub; only attribution and Settings wiring differ.

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 the live deployment—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 a repo linked under your GitHub account or use the zip round-trip described above.

7) Where to find the repository

• Decks under Superprez-managed hosting may hide repo URLs in the UI—download zip from the dashboard if you need offline access.
• Personal or connected repos: open View on GitHub from Superprez when that link is shown.
• Search your own GitHub for repos created when you chose personal hosting.