# S2 Claude context architecture How S2 layers context into Claude Enterprise so the right information reaches the right people automatically. Three tiers: org-wide (everyone, always on), group (shared by team or campus, applies inside shared Projects), individual (each person's own profile). Built for the AI at S2 initiative. Monica is the pilot; this is the template the broader staff rollout follows. --- ## Tier 1 — Organization instructions (everyone, always on) **What it is.** One block of text an admin sets once. Claude follows it in every conversation for every seat, with no action required from staff. Keep it short and high-signal: it is prepended to every chat, so length is a tax. **Where to set it.** Settings → Admin → Organization instructions. (See the "Set organization instructions" help article.) **Who sets it.** You or Monica (an Owner, or a custom admin role with the right access). **Draft to paste in (edit the bracketed parts):** > You are assisting staff at School in the Square (S2), a growing public charter > school network in Washington Heights / Inwood, Manhattan, serving about 1,000 > students across four campuses, currently Pre-K through 10th grade and adding a > grade each year (11th in 2026-27, 12th in 2027-28) toward a full Pre-K–12: > High School and Central Office (12 Sherman Ave), > Middle School (120 Wadsworth Ave), Bilingual Elementary (108 Cooper St), and > Bilingual Early Childhood (37 Park Terrace East). Two campuses are bilingual in > English and Spanish; Spanish-language parity matters for anything family-facing. > > S2's posture on AI is structured, transparent, and equity-positive. Default to > disclosure: when you help produce something that will be graded, sent to > families, or that represents the school, remind the user to review it and to > disclose AI assistance per S2 policy. > > Student data may be used inside approved S2 Claude Enterprise tools as needed > for legitimate educational work. Do not put student personally identifiable > information into any AI tool that is not on the S2 Approved Tools List. > > Voice: warm, plain-spoken, family-friendly. Avoid corporate jargon. For > family communications, offer an English version and a Spanish version. > > [Add: any S2-specific acronyms, the current school year, key dates, links to > the staff AI policy.] **Watch-out.** Org instructions are visible to every seat, so the instruction *text itself* must not contain student PII or anything person-specific. Permitting staff to work with student data inside Claude (above) is different from writing student data into this broadcast block (never do that). See the student-data gate below before enabling the permissive language. --- ## Tier 2 — Group-shared Projects (by campus and by function) **What it is.** A Project bundles instructions plus a knowledge base of files that Claude reads on every chat inside it. Share a Project with a group and that group gets the shared context and materials. Applies when members work inside the Project, not in their loose chats, so coach people to start work in the right Project. **Where to set it.** Create groups under Settings → Admin (manually, or synced from your identity provider via SCIM). Create a Project, add instructions and upload files to its knowledge base, then Share it with the group. ### Proposed group structure Two cuts, because people belong to both a campus and a function: **By campus** - High School + Central Office - Middle School - Bilingual Elementary - Bilingual Early Childhood **By function** - Central office / operations (finance, data, development, ops) - Instructional staff - School leadership (principals, directors) Groups also let you scope tools to match the Approved Tools List: e.g., Claude for everyone. ### Shared Project template — "Data & Finance" (Monica's pilot) **Project instructions:** > This project supports S2's data and finance work. Default to precision and > show your work on any calculation. When you produce numbers that will go to the > board or leadership, state your assumptions and flag anything you inferred. > Match the format of the templates in the knowledge base. **Knowledge base (upload):** - S2 org chart and campus list - Fiscal calendar and budget cycle dates - Board-deck template and a past example (de-identified) - Zoho export formats / field definitions Monica works with - Chart of accounts or budget category definitions - [no student PII; finance aggregates only] ### Other Projects to stand up next - Development / fundraising (donor comms, grant templates, the voice guide) - Principals' office (family letters, scheduling, common templates per campus) - Instructional (lesson and material templates, the Five Levels prompt starters) --- ## Tier 3 — Individual profile instructions (each person) **What it is.** Each person's own "what should Claude know about you and how should it respond." Personal, not shared. Ten minutes. **Where to set it.** Each user: Settings → Profile / personalization → "What should Claude know about you" and "How should Claude respond." **Template to hand staff:** > - My name and role: [name], [title] at [campus]. > - What I teach / do: [grade band and subjects, or function and main > responsibilities]. > - Tasks I do often that I'd like help with: [e.g., weekly family newsletter, > exit-ticket feedback, board memos, IEP-aware lesson adaptation — describe the > real recurring ones]. > - How I like responses: [length, tone, bullet points vs prose, reading level]. > - My context: [bilingual classroom? specific curriculum? anything Claude > should always assume about my students or families — without naming > individual students]. > - Avoid: [jargon, emojis, over-explaining, whatever you don't want]. **Coaching note.** This is the easiest tier to skip and the one that makes Claude feel personal, so it's the hook for the PD session. "Spend ten minutes on this and Claude stops feeling generic." --- ## Rollout sequence 1. You/Monica set the Tier 1 organization instructions once. 2. Build Monica's "Data & Finance" Project live as the pilot, capturing the steps. 3. Stand up the campus and function groups (via SCIM from your identity provider if possible, so membership and offboarding are automatic). 4. Publish 3–4 shared Projects to the right groups. 5. Roll out the Tier 3 profile template to all staff as a 20-minute recipe; fold it into a Track A module and a monthly workshop. ## Student data: the compliance gate S2 wants Claude to work with student information, and Enterprise is the right plan for it. But the deciding factor is legal, not the plan tier. Confirm these before enabling staff to put student PII into Claude: - **NY Education Law 2-d.** A 2-d-compliant data privacy agreement with Anthropic covering student data, to the same standard S2 held Flint to. This is the gate. Anthropic's standard commercial DPA may need an education-specific addendum to satisfy 2-d's prescribed terms (parents' bill of rights, security, subcontractor handling). - **FERPA.** Confirm the use fits S2's FERPA posture (school official / legitimate educational interest). - **Retention.** Standard Enterprise retains data for a configurable window (30-day minimum), and zero-data-retention is not available on the frontier ("Covered") models. Set and document the retention period you accept. - **Configuration.** Training-off is the Enterprise default; confirm it. Turn on audit logging. Decide which groups may handle student data via role-based permissions. Until the DPA is confirmed, keep the conservative posture (no student PII into Claude yet). Once it is, the Tier 1 language above permits it inside approved tools. This is a legal call for whoever owns S2's student-data agreements; the notes here are not legal advice. ## Cross-cutting watch-outs - The org-instructions *text* and shared knowledge bases are broadcast/visible within their scope, so don't write student PII into those artifacts even once the DPA is in place. Working with student data inside a chat is the permitted use; embedding it in shared config is not. - Tier 1 is automatic; Tiers 2 and 3 require people to work in the right Project and to fill in their profile. Build that habit in the PD. - SCIM/SSO is an IT coordination step, not a casual toggle. Loop in whoever runs S2's Google Workspace before enabling it.