{"resourceId":"csuchico-chatgpt-edu-api-thirdparty-controls","versions":[{"version":"external-c33c8ef7515788be23bb26fbc834c18f1f7b4be03c1730ff6e8daf15bc47f49d","resource":{"id":"csuchico-chatgpt-edu-api-thirdparty-controls","title":"Chico State ChatGPT Edu FAQ: API access disabled; third-party GPTs restricted","organization":"California State University, Chico","sector":"Public higher education (CSU)","geography":"United States (California)","publishedAt":"Undated institutional FAQ (CSU ChatGPT Edu rollout referenced from April 2025; contract window Feb 2025–July 2026)","publicationDate":null,"eventDate":null,"sourceName":"Chico State Division of Information Technology","sourceLabel":"Institutional AI service guidance","sourceUrl":"https://www.csuchico.edu/about/office/information-technology/about/strategic/artificial-intelligence/chatgpt-edu.shtml","evidenceClass":"standards-guidance","outcomeClass":"mixed","topics":["data-security","governance-procurement","developers-agents","accessibility-workforce"],"finding":"Chico State’s ChatGPT Edu FAQ documents enterprise AI for staff/students under a CSU Chancellor’s Office agreement with commercial data protections (no training on institutional conversations; SSO/SCIM). For admin control, the campus states ChatGPT API access is currently disabled and cannot be granted, and third-party GPTs are restricted to prioritize privacy/security—while custom GPTs can be built/shared in campus workspaces and web search remains available. Admins see aggregate usage metrics, not individual prompts, except narrow legal/cyber exceptions. Why now: same-week SIS/ERP agent packaging makes workspace-level least-privilege controls newly relevant for campus operations AI.","sledRelevance":"Concrete U.S. public-university control plane for enterprise generative AI used in administrative productivity: disable programmable API/Actions-like connectivity while still offering sanctioned assistants.","evidence":"Opened Chico State FAQ pages stating API access is disabled and cannot be granted; third-party GPTs restricted for privacy/security; custom GPTs allowed in campus workspaces; non-training commitment and aggregate-only admin analytics described.","architectureImplications":"Central Edu workspace with SSO/SCIM, custom GPTs inside the tenancy, and hard blocks on API/external GPT connectivity—favoring governed assistants over freely networked agents.","governanceImplications":"System-funded enterprise tool plus campus FAQ creates an approved path; Innovation Request process is the escape hatch for novel API ideas rather than silent shadow use.","securityPrivacyImplications":"Disabling API and third-party GPTs reduces exfiltration and unvetted tool chains; residual risk remains in user paste of sensitive data into the sanctioned model and in legal/cyber break-glass access.","caveats":"FAQ is institutional guidance, not an independent audit of effectiveness. No quantitative shadow-AI reduction or admin productivity metrics. Contract end (July 2026) implies renewal risk. Publication date on the page is not explicit.","streamIds":["campus-operations"],"roles":{"sales":"Public-campus CIOs wrestling with staff AI use will recognize Chico’s pattern: fund Edu centrally, keep web research, and kill API plus third-party GPT sprawl. Position a governance/enablement engagement around approved workspace configuration and exception tickets—not a new model vendor. Interpretation only: controls are documented clearly, but this FAQ does not prove shadow-AI reduction or admin service-quality gains.","engineering":"Fit for institutions standardizing on ChatGPT Edu (or similar) for admin productivity. Integrate SSO/SCIM, mirror API-disabled and third-party GPT restrictions, and document an Innovation Request exception path. Prerequisites: enterprise contract, data-classification guidance, and admin-console ownership. Constraints: blunt workspace controls, not task-scoped agent permissions. Security: pair blocks with DLP and training so sensitive admin data is not pasted into even sanctioned chats.","delivery":"Delivery is configuration, communication, and literacy—not a greenfield build. Work includes admin-console baselines, custom GPT patterns for admin units, and exception ticketing. Ownership: DoIT with HR/finance/registrar content owners for unit GPTs. Proposed acceptance criteria: API remains disabled; third-party GPT policy published; aggregate usage dashboard live. Risk: over-restriction that drives staff back to personal tools."},"roleDetails":{"sales":{"customerProblem":"Staff need sanctioned AI for admin work while IT must limit programmable/external GPT connectivity that creates data risk.","stakeholders":["CIO","CISO","HR/finance/registrar leaders","Faculty senate / staff council"],"discoveryQuestions":["Is ChatGPT API or equivalent agent connectivity enabled today?","How are third-party GPTs reviewed or blocked?","What exception path exists for legitimate admin integrations?"],"valueHypothesis":"Workspace least-privilege plus a usable Edu assistant can reduce shadow AI if approved tools stay competitive on speed.","potentialEngagement":"One-week Edu control-plane review: API/Actions/GPT sharing settings, exception workflow, and admin unit GPT patterns.","unsupportedClaims":["Elimination of shadow AI","Measured productivity gains from Edu","FERPA-safe use without user training"]},"engineering":{"fit":"CSU-like public institutions deploying ChatGPT Edu for campus-wide staff/student productivity with central admin controls.","architectureIntegration":"SSO/SCIM into Edu tenancy; custom GPTs only inside campus workspace; keep API and third-party GPT surfaces off by default.","prerequisites":["Enterprise Edu contract","Identity lifecycle (SCIM)","Published data-classification and acceptable use"],"constraints":["Workspace-level blunt controls","Contract term/renewal window","No task-scoped agent permissions in FAQ"],"security":"Maintain API off and third-party GPT restrictions; limit admin visibility to aggregates; define legal/cyber break-glass.","proofOfValue":["Config screenshot/export showing API disabled","Sample of blocked third-party GPT attempts","User survey on sanctioned vs personal tool use"]},"delivery":{"work":"Configure Edu controls, publish FAQ/policy, train staff, and stand up Innovation Request exceptions.","dependencies":["Chancellor’s Office / campus licensing","DoIT admin console access","Communications to employees/students"],"ownership":"Division of Information Technology with unit GPT owners.","skillsAdoption":"Self-paced AI literacy plus support labs so sanctioned tools remain usable.","governanceCheckpoints":["Control baseline review each term","Exception ticket audits","Contract renewal security review"],"acceptanceCriteria":["API access remains disabled in production","Third-party GPT restriction documented for users","Aggregate usage metrics available to admins"],"risks":["Usability friction → shadow AI","Sensitive paste into sanctioned chats","Contract lapse removing protections"]}},"retrievedAt":"2026-10-03T21:58:10-05:00","enrichedAt":"2026-10-03T21:58:10-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"System-funded licenses aim to close equity gaps for employees/students; FAQ does not measure admin workload change or accessibility conformance of the Edu UI.","procurementImplications":"Illustrates system-level Edu purchasing (CSU Chancellor’s Office) with campus-operated controls—procurement should negotiate non-training, SSO/SCIM, and admin control features explicitly.","operatingModelImplications":"Approved AI path with hard limits on programmable connectivity; innovation requests replace ad-hoc API enablement.","sourceVerification":{"openedUrl":"https://www.csuchico.edu/about/office/information-technology/about/strategic/artificial-intelligence/chatgpt-edu.shtml","referenceExcerpt":"access to the ChatGPT API is currently disabled and cannot be granted.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}