Heidelberg AI Curriculum

5books in this track

L01 · User

Who is affectedOnly you

Get Answers You Can Use from a Chatbot

Put the material, the reader, an example and the exclusions into one chat request, then improve the answer with follow-ups that change one thing at a time, so you can say which change fixed it and reuse it.

Outcome: A before/after pair from your own notes, with the one follow-up that fixed it, which passes when a colleague can see the improvement and finds nothing in the final version that isn't in your notes.

User13 minLast edited: Sep 23, 2026

L02 · Power user

Who is affectedYour team sees a bad document or a wrong figure

T02-L02

Set Up Projects a Colleague Can Pick Up

Stop pasting the same background into every chat. Give each job its own project with instructions, source files and a dated decisions file, keep memory from carrying one job into another, and set it up so a colleague can continue your work in a fresh chat while you're away.

Outcome: A project for one real team job, with instructions, source files and a dated decisions file whose master copies sit in a shared folder, and a colleague's continuation in a fresh chat. It passes when the continuation follows the current decision, not an old one, and the colleague needed nothing from you beyond the project and its folder.

Power user15 minLast edited: Sep 23, 2026

L03 · Builder

Who is affectedColleagues depend on something you built

T02-L03

Build a Shared Assistant Your Team Can Test and Take Over

Turn one recurring team question into a shared assistant: current sources only, pinned instructions and model, use and edit rights kept apart, and a test set that runs before every change goes live. It passes when your deputy updates a source, reruns the tests and publishes without you.

Outcome: A shared assistant for one recurring team job, with a usage note, a test set of at least ten known-answer questions and a change log; it passes when your deputy replaces one source, reruns the test set, publishes the new version and a colleague gets the updated answer, all without your help.

Builder18 minLast edited: Sep 23, 2026

L04 · Integrator

Who is affectedCompany or lab systems and real data are in the loop

T02-L04

A Self-Hosted Assistant Your Team Can Use Safely

Start Open WebUI with Heidelberg AI Desk on one machine, connect a local model or a provider key, and learn where every prompt goes. Then do the Level 4 part: decide who can reach the assistant, how accounts are approved, and which data it may see, before colleagues log in.

Outcome: A one-page assistant record (model and where prompts go, who can reach it, how accounts are approved, who administers it, allowed data classes, backups) plus Open WebUI running on one machine with a non-admin test account; it passes when the test account can chat but can't open the Admin Panel, sign-up is off, and a colleague answers three paste questions correctly from the record alone.

Integrator20 minLast edited: Oct 12, 2026

L05 · Operator

Who is affectedWork stops when it breaks, and it must survive you leaving

T02-L05

Run One Assistant for a Whole Institute or Company, and Hand It Over

When 150 people use one assistant, its doors, budgets and records are yours to run. Put everyone behind the organisation's login, end a leaver's access with one tested action, give each group a budget, keep lean records, and hand it all to a substitute.

Outcome: An access audit for the shared assistant: every account, role, key and emergency access with its owner and revocation path, a tested one-action leaver removal, group budgets with last month's cost per group, the records and retention table signed by the data protection officer, and the substitute's run. It passes when a test leaver loses a live session and a fresh login within the stated window after one action, no local password login works, and the substitute repeats the audit from the runbook alone.

Operator20 minLast edited: Sep 23, 2026