Setup guide for educators

Contact your institution administrator to receive an invite link, or register directly if self-hosting. Access uses passkeys — no password to remember.

Invited educators receive a one-time registration link via email.

Generate a personal access token in GitLab with read_api and read_repository scopes. Paste it in your profile settings.

The token is stored encrypted and used only to discover and clone repositories in your GitLab group.

Admins create units and assign educators. Each unit maps to one GitLab group — for example, your subject's GitLab namespace where student repos live.

Set the unit code, semester, year, and the GitLab group URL. These are used to generate student result URLs.

On the unit page, click "Import from GitLab" to discover all repositories in your GitLab group. Each discovered repository becomes trackable.

Re-import at any time to pick up new repositories added after the semester started.

Set up grading criteria, weights, and thresholds for this unit. You can enable or disable specific criteria and adjust what each band requires.

Start with the default rubric and adjust after your first run to see where the cohort lands.

Clone all repositories locally (Step 2 in the unit pipeline), then trigger a full-unit marking run. Results are available in under 10 minutes.

For large cohorts (>100 repos) budget 15–20 minutes for the first clone. Subsequent runs are faster as only new commits are fetched.

Explore the cohort heatmap, flag at-risk students, add marker notes, and send each student their personalised feedback URL.

Use the "Share Results" button on the unit page to copy a public link you can post in your LMS.

Add a CI job to your GitLab group's CI template that calls the AgenticEd API after each push. Runs trigger automatically without manual intervention.

See the webhook snippet on your unit page for the exact YAML to add to your .gitlab-ci.yml file.