From the Campus Operations edition of October 19, 2026
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
Emory University (Office of Information Technology; Office of the Provost) · Private research university: enterprise AI access for staff, faculty and students · Atlanta, Georgia, United States
- Publisher
- Emory News Center
- Original publication
- 19 October 2026 (Emory News)
- Source retrieved
- 2026-10-20
- Event date
- 2026-10-19
What happened
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.
Why it matters
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 and measured results
University news announcement quoting the provost's office and CIO. No contract value, seat counts, adoption targets or evaluation method.
Limitations and uncertainty
Announcement only; no outcomes. Pilot criteria for Code and Cowork are not described. Premium price is per the announcement.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-19; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- 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
- Discovery questions
- How many personal Claude accounts use institutional email?
- What criteria will decide the Code and Cowork pilots?
- How will premium seat demand be tracked?
- Value hypothesis
- Interpretation: a structured pilot evaluation could shorten the agentic-tools decision; not shown by this source.
- Potential engagement
- A pilot evaluation design for agentic tools, or a personal-account migration plan, for one campus.
- Unsupported claims
- Productivity or cost savings
- That Code and Cowork are safe for restricted data
- Adoption levels
Pre-sales engineering
Role takeaway
- Fit
- Enterprise SSO tenant for general AI use; agentic tools pending.
- Architecture and integration
- 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.
- Proof of value
- Migrate a sample of existing accounts and confirm data retention
- Pilot Code and Cowork with logged actions on non-restricted data
Delivery
Role takeaway
- 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.
- Skills and adoption
- Self-guided training through vendor academy and OIT pages; more promised.
- Governance checkpoints
- Pilot review before adding Code or Cowork
- Data-class guidance acknowledgement
- Acceptance criteria
- 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
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
SSO-based enterprise tenant with a pending migration of existing email-verified accounts into it; agentic desktop tools excluded for now.
Governance
Who approves, reviews and stays accountable for outcomes?
Request-based access and a pilot gate for agentic features; individual responsibility for verifying output and following policy.
Security and privacy
What data, permissions and controls need testing?
Restricted data, PHI, CUI and identifiable student information are excluded, which limits use in health, registrar and HR workflows.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Free standard tier lowers cost barriers; premium access depends on department budgets, which may create uneven access.
Procurement
What should contracts, pricing and exit terms secure?
Chargeback model ($50 per premium seat per month) moves AI cost to departments; consolidating personal subscriptions is part of the rollout.
Operating model
Which teams own the service once it runs?
OIT runs request intake, licensing tiers, migration and pilots as separate workstreams.
Publication history
- 2026-10-19Campus Operations · Issue 429 resources
Stable resource ID: emory-claude-edu-request-access-department-premium-20261019