Your path from account to research

Secure your research account before accessing machines

Verify your email address, complete your research profile, enable multi-factor authentication, and register only your public SSH and WireGuard keys. Do not upload private keys or recovery codes.

Key registration is a request for provisioning, not proof that a tunnel or SSH account is already active.

Student or existing research member? Request a programme membership

Sign in, complete your profile, visit Research Programmes and request membership in an existing programme. Your PI or programme administrator reviews it. A registered account alone has no GPU or QPU allocation.

Principal investigator? Apply to lead a programme

Provide your institution, programme name and research description in the PI application. Your application is reviewed before a programme is approved and members can receive entitlements.

Check your resource entitlements

After programme and identity approval, verify which CPU, A100/H200 GPU or remote QPU resources are actually allocated. You must have the necessary environment and provider authorization before submitting a hardware workload.

Launch Workbench, then submit a small CPU Slurm job

Open Jupyter Workbench with your provisioned research identity. Begin with an available local notebook, then use Runs to submit an approved CPU reference workflow. Record its job ID, scheduler status and result manifest. A submitted job is not yet a completed result.

Using an SSH shell? Submit through the existing Slurm client (sbatch, squeue, sacct) after your account and scheduler allocation are ready. Interactive zsh is optional and does not change job shebangs.

Continue your learning journey with Quantum Guide

Use Guide for explanations, research navigation and approved notebook references. It is not a substitute for executing and validating scientific code. Your conversations and permissions belong to the research account; terminal connections require explicit authentication.