{"resourceId":"emory-claude-edu-request-access-department-premium-20261019","versions":[{"version":"external-e3f9cf4cdc70bc636bfe05e4e49dd4e9cb37e3491539f2c5de1b99277f75015f","resource":{"id":"emory-claude-edu-request-access-department-premium-20261019","title":"Emory offers Claude for Education by request, with free standard seats, $50-a-month department-paid premium seats, and Claude Code and Cowork held back for pilots","organization":"Emory University (Office of Information Technology; Office of the Provost)","sector":"Private research university: enterprise AI access for staff, faculty and students","geography":"Atlanta, Georgia, United States","publishedAt":"19 October 2026 (Emory News)","publicationDate":"2026-10-19","eventDate":"2026-10-19","sourceName":"Emory News Center","sourceLabel":"Institutional announcement","sourceUrl":"https://news.emory.edu/stories/2026/10/claude-ai-available-emory-university-community","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["knowledge-work","developers-agents","data-security","governance-procurement"],"finding":"Emory made Claude for Education available by request to students, faculty and staff with active accounts. Standard licenses cost nothing; premium licenses with higher usage cost $50 per license per month, paid by departments. The initial offering covers Claude, Projects, Artifacts and Learning Mode. Claude Cowork and Claude Code are excluded and are being evaluated in limited pilots. Users must not enter PHI, CUI, identifiable student information, passwords, credentials or other restricted data. People with existing Claude accounts under an Emory email are told not to use Emory SSO yet; OIT will contact them about migration.","sledRelevance":"Adds another research university to managed-seat AI access and shows a common operational shape: free baseline seats, department-paid premium seats, agentic tools held back for pilots, and a migration problem for staff who bought personal accounts with institutional email.","evidence":"University news announcement quoting the provost's office and CIO. No contract value, seat counts, adoption targets or evaluation method.","architectureImplications":"SSO-based enterprise tenant with a pending migration of existing email-verified accounts into it; agentic desktop tools excluded for now.","governanceImplications":"Request-based access and a pilot gate for agentic features; individual responsibility for verifying output and following policy.","securityPrivacyImplications":"Restricted data, PHI, CUI and identifiable student information are excluded, which limits use in health, registrar and HR workflows.","caveats":"Announcement only; no outcomes. Pilot criteria for Code and Cowork are not described. Premium price is per the announcement.","streamIds":["campus-operations"],"roles":{"sales":"Sales framing: Emory's launch shows the problems that follow a campus AI license: department chargeback, personal accounts to migrate, and agentic tools waiting on pilot results. Bounded help is a pilot evaluation plan for Claude Code and Cowork or a personal-account migration plan. Do not claim productivity gains; the announcement reports none, and pilot criteria are not public.","engineering":"Engineering framing: the technical work is identity and tenant consolidation, moving email-verified personal accounts into the SSO tenant without losing users' data, plus data-class enforcement since restricted data is excluded. For the Code and Cowork pilots, define what local file and system access is allowed and how actions are logged before widening access. Also confirm how premium licenses are assigned and revoked when departments stop paying.","delivery":"Delivery framing: three tracks run at once (request-based provisioning, premium chargeback and account migration) while pilots decide on agentic tools. OIT owns provisioning; departments own premium budgets. Proposed acceptance: migration completed with no data-loss reports, and a written pilot decision on Code and Cowork with stated criteria. Track premium seat counts by department so uneven access is visible, and publish the pilot criteria before results come in."},"roleDetails":{"sales":{"customerProblem":"A university rolling out an enterprise AI license must handle chargeback, personal accounts and a decision on agentic tools.","stakeholders":["CIO","Provost's office","Department administrators","Information security","Research computing"],"discoveryQuestions":["How many personal Claude accounts use institutional email?","What criteria will decide the Code and Cowork pilots?","How will premium seat demand be tracked?"],"valueHypothesis":"Interpretation: a structured pilot evaluation could shorten the agentic-tools decision; not shown by this source.","potentialEngagement":"A pilot evaluation design for agentic tools, or a personal-account migration plan, for one campus.","unsupportedClaims":["Productivity or cost savings","That Code and Cowork are safe for restricted data","Adoption levels"]},"engineering":{"fit":"Enterprise SSO tenant for general AI use; agentic tools pending.","architectureIntegration":"SSO tenant; migration from email-verified personal accounts; projects and artifacts within the tenant.","prerequisites":["Data classification guidance","Account migration tooling","License tier management"],"constraints":["No restricted, PHI, CUI or identifiable student data","Agentic tools excluded for now"],"security":"Data exclusions rely on user compliance; no technical data-loss prevention is described.","proofOfValue":["Migrate a sample of existing accounts and confirm data retention","Pilot Code and Cowork with logged actions on non-restricted data"]},"delivery":{"work":"Run provisioning, premium chargeback, account migration and agentic pilots in parallel.","dependencies":["Vendor migration support","Department budgets","Pilot volunteers"],"ownership":"OIT owns the service; departments own premium spend.","skillsAdoption":"Self-guided training through vendor academy and OIT pages; more promised.","governanceCheckpoints":["Pilot review before adding Code or Cowork","Data-class guidance acknowledgement"],"acceptanceCriteria":["Proposed: all institutional-email personal accounts migrated or closed by a set date","Proposed: documented go/no-go on agentic tools"],"risks":["Users lose work during migration","Uneven premium access","Restricted data entered despite rules"]}},"retrievedAt":"2026-10-19T21:56:40-05:00","enrichedAt":"2026-10-19T22:05:34-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Free standard tier lowers cost barriers; premium access depends on department budgets, which may create uneven access.","procurementImplications":"Chargeback model ($50 per premium seat per month) moves AI cost to departments; consolidating personal subscriptions is part of the rollout.","operatingModelImplications":"OIT runs request intake, licensing tiers, migration and pilots as separate workstreams.","sourceVerification":{"openedUrl":"https://news.emory.edu/stories/2026/10/claude-ai-available-emory-university-community","referenceExcerpt":"Premium licenses provide higher usage allowances and are available at $50 per license per month, funded by individual departments.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}