Repository navigation
Getting started
The first-time user landing page is now described in the portal source at
/getting-started/.
The release may not yet be deployed; source/CI and live access are separate.
- Create an account and verify your email.
- Complete research identity and enable MFA.
- Register only public SSH and WireGuard keys. Never paste a private key or recovery code into the portal or Guide. Registration is distinct from actual provisioning.
- A student requests membership in an existing research programme; a PI applies via the PI application page. Approval is not automatic.
- Check resource entitlements before trying CPU/GPU/QPU workloads.
- Launch Workbench and run a small approved CPU notebook. Use Runs for scheduler-managed execution; record the Slurm job ID and artifact manifest.
A verified account plus programme membership request does not imply automatic POSIX/SSH/VPN provisioning or GPU access. Once the PI and operator approve resources, the portal can expose its Workbench and scheduler paths. Only use an approved scheduler allocation; do not share another user's account.
A programme application creates a review request, not a live resource pool. Programme owners/members, quotas and research permissions remain separate from account signup. Confirm the membership and capacity allocation before telling students that hardware is available.
Login nodes preserve their existing login shell. zsh is installed only as
an optional interactive shell; run zsh to opt in for that session
and exit to return. This never changes a Slurm script's #!/bin/bash
shebang or its scheduler authorization.
Herdr reconnects per-user terminal panes; ACP PostgreSQL remains the source
for persistent researcher chats, not saved terminal output. The current
acp --browser-pair path is an authentication conformance fallback,
not the planned repeated daily UX. This feature is tracked in
ACP #88.
The reviewed editorial plan proposes short signup, MFA, SSH/WireGuard, PI, student, Workbench, Slurm and agent status videos. No videos have yet been released. Never record private keys, JWTs, live user names, allocations or private workspaces for a tutorial.
More: Account and access, Researcher guide and Workbench and runs.
Quantum Platform
- Home
- Getting started
- Account and access
- Researcher guide
- Workbench and runs
- Agent and Guide
- Administrator guide
- Developer guide
- API and integration
- Troubleshooting
- Security
- Contributing
- Guide integration and support Detailed topics
- Programme approval and resource entitlements
- Authentication MFA and key management
- JupyterHub and SSH identity
- API development and tests
- Research programme administration Guide integration
- Guide knowledge and source ingestion
- Guide support and ticket workflows