{"resourceId":"umd-claude-enterprise-standard-premium-seats-level-3-data-20261028","versions":[{"version":"external-9de8a8dbdcbfd2fc76dda52a04475b94281b549f76d8f8f98b4feded0592fec8","resource":{"id":"umd-claude-enterprise-standard-premium-seats-level-3-data-20261028","title":"University of Maryland offers Claude for Enterprise to faculty and staff at $20 and $55 department-paid seat tiers, approved for Level 3 high-risk data, with Premium seats from the week of Nov. 2","organization":"University of Maryland, Division of Information Technology","sector":"Higher education","geography":"Maryland, United States","publishedAt":"October 28, 2026","publicationDate":"2026-10-28","eventDate":"2026-11-02","sourceName":"UMD Division of Information Technology","sourceLabel":"University IT announcement","sourceUrl":"https://it.umd.edu/news/claude-enterprise-available-umd","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["governance-procurement","data-security","developers-agents","operating-model"],"finding":"UMD's IT division says Claude for Enterprise is available to faculty, staff and researchers through department-funded seats: Standard at $20 per seat per month and Premium at $55 per seat per month, the latter meant for long Claude Code or Cowork agentic sessions and following the week of Nov. 2. Both tiers carry the same models and tools under UMD SSO and data protections, and Claude is approved for data classified up to Level 3 - High risk.","sledRelevance":"Directly relevant to higher-education buyers comparing seat models: it publishes per-seat prices, a usage-based tier split and a data-classification approval. Cross-tagged campus-operations because it describes central IT licensing and chargeback. Published Oct. 28 (before the last run) but not archived; why now: Premium seats arrive the week of Nov. 2.","evidence":"Operator (university IT) announcement; classed as vendor-claim consistent with other university service announcements in this archive. No outcome data.","architectureImplications":"Same models and tools across tiers means the tier choice is about usage limits, not capability; agentic Claude Code and Cowork use drives the Premium tier.","governanceImplications":"Level 3 high-risk data approval is a significant institutional decision; units must still apply UMD AI-use guidelines.","securityPrivacyImplications":"Approval up to Level 3 implies a completed institutional risk review; buyers elsewhere should not assume equivalent approval without their own review.","caveats":"Prices are UMD's institutional rates and may not transfer to other campuses. No information on student access or usage outcomes.","streamIds":["anthropic","campus-operations"],"roles":{"sales":"The sales point is a published campus price and tier benchmark. UMD charges departments $20 or $55 per seat per month, with the higher tier for heavy agentic use, and approved Claude for Level 3 high-risk data. Campus buyers can use this to frame seat-mix and chargeback questions. Ask how they expect usage to split between light and heavy users. Do not quote UMD's rates as available elsewhere or imply its data approval transfers to another institution.","engineering":"For engineers, the notable details are identical models and tools across tiers and a Level 3 data approval. Tier choice is about usage limits, driven by long Claude Code and Cowork sessions. Engineers advising other campuses should help estimate agentic usage before seat purchase, confirm SSO and administration integration, and run their own data-classification review rather than citing UMD's approval.","delivery":"Delivery should plan seat management as ongoing operations. UMD uses a request form, department chargeback and a staged Premium tier. A delivery lead elsewhere would define request and approval flow, monitor usage to move users between tiers, and document data-classification limits for users. Acceptance criteria should be proposals, such as request turnaround and tier-fit reviews, since UMD reports no outcomes."},"roleDetails":{"sales":{"customerProblem":"Campuses need to choose seat tiers and fund them without data on how usage will split.","stakeholders":["CIO","Research computing leads","Department business officers","Information security office"],"discoveryQuestions":["How many users would run long agentic sessions?","Will departments pay for seats directly?","What data classification would Claude be approved for?"],"valueHypothesis":"Interpretation: a two-tier seat model may help match cost to usage, if usage can be monitored.","potentialEngagement":"A bounded seat-mix and chargeback planning exercise using published campus benchmarks.","unsupportedClaims":["That UMD prices apply elsewhere","That Level 3 approval transfers","Any productivity outcome"]},"engineering":{"fit":"Fits campuses already using SSO-integrated SaaS with departmental chargeback.","architectureIntegration":"SSO and central administration; tiers differ only in usage limits.","prerequisites":["SSO integration","Data-classification review","Usage reporting by user"],"constraints":["No student access described","Usage limits defined relative to vendor plans","Department funding may limit reach"],"security":"Level 3 approval at UMD reflects its own review; other institutions must review independently.","proofOfValue":["Measure agentic usage during a trial before buying Premium seats","Confirm admin controls meet local classification rules","Verify usage reporting supports tier changes"]},"delivery":{"work":"Stand up a seat request, chargeback and tier-review process.","dependencies":["Procurement contract","Finance chargeback","Identity management"],"ownership":"Central IT service owner.","skillsAdoption":"Users need guidance on data classification; heavy agentic users need Claude Code or Cowork onboarding.","governanceCheckpoints":["Security review of data classification","Quarterly tier-fit review","Annual renewal review"],"acceptanceCriteria":["Proposal: seat requests fulfilled within a stated service level","Proposal: quarterly review moves under-used Premium seats","Proposal: 100% of users acknowledge data-classification guidance"],"risks":["Uneven access across departments","Overbuying Premium seats","Users exceeding approved data levels"]}},"retrievedAt":"2026-11-01T03:05:00Z","enrichedAt":"2026-11-01T03:11:01Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Department-paid seats may create uneven access across units.","procurementImplications":"Publishes comparable campus seat prices and a two-tier model useful for benchmarking.","operatingModelImplications":"Chargeback to departments and a request form make seat management an ongoing central IT task.","sourceVerification":{"openedUrl":"https://it.umd.edu/news/claude-enterprise-available-umd","referenceExcerpt":"Claude is approved for data classified up to Level 3 - High risk, and UMD's AI-use guidelines apply.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}