--- name: onboarding description: Use when a Cottonwood volunteer wants to learn ChatGPT, understand library tools and account roles, work through the volunteer academy, or rehearse a library task without changing real services. --- # Volunteer onboarding Follow library-assistant. The academy is at `https://www.cottonwoodcommunitylibrary.com/academy/`; its lesson source is `src/pages/academy/_guide.ts` in the maintained repository. Use current main. If the page is not live yet, teach from the available lesson source and say the hosted guide is pending; do not give a broken link as a working resource. Read the wiki skill’s `references/academy.md` for the matching lesson, service or example. It contains the full academy, including the quick guide and technical reference. Ask where they want to begin only if unclear. Offer one small action, say what they should see after it, wait for their reply, and adapt the pace. Do not assume computer experience based on age. If a label is unfamiliar, explain it before asking them to use it. For a beginner, start with Your first chat, then use Find your way around for unfamiliar tabs and menus. Photos, files and links covers attachments; ChatGPT for library work introduces the connected library tools. Follow with the requested task. Keep Behind the scenes optional unless they ask about those systems. Explain unfamiliar terms through the task: a skill supplies instructions; a connection supplies access. Neither proves a live operation works. Do not make volunteers pick technical tools or use Codex, GitHub or Sanity for routine work. ## Teach through the requested task Use the academy’s actual jobs: add an event, correct a page, upload a newsletter, send an Engage email, find newsletter subscribers, prepare a Facebook post or record a received cash/check donation. Give the real button or page name when the person has to click something. Explain what that step accomplishes. Write ordinary examples such as “Add an event to the website” or “Make this announcement shorter.” Do not make volunteers learn internal tool names, publishing checks, receipt validation or safety instructions to phrase a request. Handle those requirements yourself. Avoid generic quizzes, certification language, reminders about “shifts”, and filler tasks such as “work without ChatGPT.” ## Practice has no service effects “Practice”, “training”, “simulation” and “role-play” mean chat-only exercises. Do not create even private drafts, upload assets, publish records, create PRs, schedule tasks, send messages, add subscribers, record transactions or delete anything. Use clearly fictional facts in chat. Simulate the preview and approval conversation without treating “yes” inside the exercise as a real approval. During an exercise, help them write and revise a useful result. Explain a missing date or end time when it comes up, rather than reciting a checklist. A live rehearsal requires an explicit end to practice, a genuine authorized task and the ordinary topic/publishing workflow. Never turn a training example into a real library announcement. ## Accounts and help The public academy gives service purposes and role boundaries, not a credential list. `assistant/ACCOUNT-REGISTER.md` is a private board handoff with known identities, evidence dates and unresolved access. Use only the entries needed for an authorized person's role; never copy the whole register into public pages, PDFs, screenshots or shared drafts. Never request passwords or codes. Technical help stays with ChatGPT. Follow library-assistant for supported reconnection; the board supplies library facts and approvals. Help them find the one-page task guide at `/academy/quick-reference/` and the printable handbook at `/academy/print/`. For a real platform incident, use troubleshooting rather than continuing a pretend exercise. A practice exercise does not verify the installed tools. Check those connections during an explicitly authorized real task.