First-run setup

A new instance has no users. The first time you open it, Jangka shows a four-step setup wizard that creates the organization and its first admin. It runs once: after it completes, the instance shows the sign-in page instead.

1. Setup token

The token proves that you control the server. Jangka prints it to the container's output, not to the JSON log stream, and stores only a hash of it.

docker logs jangka 2>&1 | grep "SETUP TOKEN" | tail -n 1

Until setup completes, every start of the app prints a new token and the previous one stops working. tail -n 1 picks the latest one. If the container restarts while you're in the wizard, the wizard sends you back to this step: read the log again and enter the new token.

2. Organization

The organization name appears in the sidebar and on exported documents.

Add example documents is checked by default. It creates an Examples collection, viewable by everyone, with a BRD, a PRD and a TSD about one feature that are linked to each other. They show what a finished spec looks like, with requirement IDs, trace links and diagrams. Archive the collection when you no longer need it. Admins can add the examples again later from the command palette (Add example documents).

3. Admin account

The first admin signs in with email and password. The password needs at least 12 characters. You're signed in as this admin when the step completes.

4. Connect an LLM

Jangka drafts with your own provider key: Anthropic, any OpenAI-compatible endpoint, or Gemini. The key is encrypted with MASTER_KEY before it's stored.

You can choose Skip for now and add a provider later. Until one exists, the assistant can't draft.

After setup

Everything the wizard set up, and what it skipped, lives under Admin: