Sign in

An email link is enough to work through the modules and keep your progress. Hands-on units and the platform exams additionally need a read-only Buildkite token, because they are verified against a real build.

Email me a link

Or sign in with a Buildkite token

Identifies you by your Buildkite account, which is what hands-on verification needs. Create one in your API access tokens, scoped to a single organisation, with exactly these scopes:

read_user read_builds read_pipelines read_agents

We refuse tokens carrying any write_ or delete_ scope, and never store the token — it is used for that request and discarded, which is why hands-on submissions ask for it again.