{"resourceId":"msu-chatgpt-edu-atlas-connectors-disabled","versions":[{"version":"external-c33c8ef7515788be23bb26fbc834c18f1f7b4be03c1730ff6e8daf15bc47f49d","resource":{"id":"msu-chatgpt-edu-atlas-connectors-disabled","title":"Michigan State ChatGPT EDU KB: Atlas browser and cross-platform connectors disabled by default","organization":"Michigan State University","sector":"Public higher education","geography":"United States (Michigan)","publishedAt":"Undated MSU IT knowledge-base article (Atlas/connector restrictions described as current policy)","publicationDate":null,"eventDate":null,"sourceName":"Michigan State University IT (TeamDynamix KB)","sourceLabel":"Institutional AI service guidance","sourceUrl":"https://tdx.msu.edu/TDClient/32/Portal/KB/Article/2275/Generative-AI-Platforms-General-Information-About-ChatGPT-EDU","evidenceClass":"standards-guidance","outcomeClass":"mixed","topics":["data-security","governance-procurement","developers-agents","operating-model"],"finding":"MSU’s ChatGPT EDU knowledge article states the Atlas Web Browser feature is disabled to protect university data and maintain data-governance compliance, and that cross-platform connectors/plugins/apps (examples: Outlook, OneDrive, SharePoint, Google Drive, Slack) are disabled because connected systems may hold data under stricter requirements than those approved for ChatGPT Edu. Custom GPTs may be shared in the MSU workspace; public sharing only with public data and no institutional/confidential/restricted information. Edu does not use institutional data for model training. Why now: as admin AI agents and ERP connectors proliferate, MSU documents a default-deny connector posture for campus operations data stores.","sledRelevance":"Operational control evidence for higher-ed admin AI: block browser/agent connectivity and SaaS connectors into email/files before those channels become silent data paths for campus operations assistants.","evidence":"Opened MSU TDX article sections answering Atlas and connectors FAQs with explicit disablement rationale tied to data governance; lists example connectors; states public CustomGPT sharing constraints and non-training stance.","architectureImplications":"Edu remains a chat/custom-GPT workspace without default bridges into campus SaaS data planes—integrations require separate security/data-governance evaluation rather than user-toggled connectors.","governanceImplications":"Separates ‘tool approved’ from ‘data source approved,’ a critical procurement/governance distinction for HR, finance, and student-record adjacent AI.","securityPrivacyImplications":"Default-deny connectors reduce unauthorized AI access to email and files; users may still paste sensitive content or use personal ChatGPT accounts the article acknowledges as allowed but unprotected.","caveats":"Institutional KB, not an audit of efficacy. No metrics on shadow AI, connector exception volume, or admin productivity. Page is undated. Personal accounts remain permitted outside MSU protections.","streamIds":["campus-operations"],"roles":{"sales":"CISOs and CIOs enabling campus ChatGPT Edu will care that MSU treats Atlas and SaaS connectors as separate risk decisions from the chat license itself. Sell a control-plane and data-governance review for email/file connectors that would support finance, HR, or registrar assistants. Interpretation: this KB documents policy posture and rationale, not measured incident reduction or productivity outcomes.","engineering":"Fit for campuses deploying Edu/enterprise LLM workspaces that also run Microsoft or Google SaaS. Architecture: keep Atlas and connectors off; require case-by-case review before linking Outlook, Drive, or SharePoint. Prerequisites: data-classification mapping of connected systems, SSO, and clear CustomGPT sharing rules. Constraints: personal accounts remain allowed outside protections. Security: assume paste risk and watch for shadow connectors elsewhere.","delivery":"Operationalize default-deny: publish KB guidance, train the service desk on exception requests, and review connector asks with security and data governance. Ownership: MSU IT generative AI platform team with data stewards for each system. Proposed acceptance criteria: Atlas off; listed connectors off; exception log exists. Risk: staff route around via personal tools when connectors stay blocked without usable approved alternatives."},"roleDetails":{"sales":{"customerProblem":"Enterprise ChatGPT is approved, but connecting it to email and campus files can violate data-governance boundaries for admin data.","stakeholders":["CIO","CISO","Data governance","HR/finance/registrar system owners"],"discoveryQuestions":["Which LLM connectors are enabled to email and file systems?","Is Atlas or equivalent browsing agent disabled?","Who approves exceptions for admin workflows?"],"valueHypothesis":"Default-deny connectors plus a clear exception path can let campuses expand Edu use without silently piping FERPA/HR data into the model.","potentialEngagement":"Connector threat-model workshop for one admin SaaS (e.g., SharePoint finance site) with allow/deny recommendation.","unsupportedClaims":["Zero data leakage under Edu","No shadow AI while personal accounts remain allowed","Measured reduction in incidents"]},"engineering":{"fit":"Institutions running ChatGPT Edu for teaching, research, and administrative productivity that also run Microsoft/Google SaaS.","architectureIntegration":"Keep Atlas and cross-platform connectors disabled; treat any connector enablement as a new data-processing approval.","prerequisites":["Data classification for email/file systems","SSO into Edu","Documented CustomGPT sharing policy"],"constraints":["Personal ChatGPT accounts still allowed","Feature availability depends on OpenAI rollout","Blunt workspace controls vs task-scoped permissions"],"security":"Default-deny connectors; restrict public CustomGPT sharing; reinforce that Edu approval ≠ connected-system approval.","proofOfValue":["Admin console evidence Atlas/connectors disabled","Exception ticket sample with review notes","Spot-check CustomGPTs for restricted data"]},"delivery":{"work":"Maintain Edu configuration, publish user guidance, route connector requests through security/data governance, and support CustomGPT sharing norms.","dependencies":["MSU Tech Store licensing","Okta SSO","AI security / data-governance reviewers"],"ownership":"MSU IT Generative AI Platform with system data owners for exceptions.","skillsAdoption":"Help desk and staff need clear scripts for why connectors are off and how to request review.","governanceCheckpoints":["Periodic connector posture review","CustomGPT sharing audits","Re-evaluation when OpenAI ships new features"],"acceptanceCriteria":["Atlas disabled in production workspace","Listed cross-platform connectors disabled by default","Exception process documented in KB"],"risks":["Shadow AI via personal accounts","Admin friction delaying legitimate work","New OpenAI features reintroducing risk if auto-enabled"]}},"retrievedAt":"2026-10-03T21:58:20-05:00","enrichedAt":"2026-10-03T21:58:20-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Edu is positioned for administrative efficiency (reports, summaries, templates); workforce impact and accessibility of the blocked-connector experience are not evaluated.","procurementImplications":"Departmental annual billing via tech store shows decentralized license ops on top of central controls—procure for admin control features (connector toggles, Atlas disable) not just seats.","operatingModelImplications":"Reinforces an operating model where AI chat is broadly available but campus data planes stay disconnected until explicitly approved—slowing agentic admin automation by design.","sourceVerification":{"openedUrl":"https://tdx.msu.edu/TDClient/32/Portal/KB/Article/2275/Generative-AI-Platforms-General-Information-About-ChatGPT-EDU","referenceExcerpt":"The Atlas Web Browser feature is currently disabled in MSU's ChatGPT Edu environment.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}