education-cloud-eda-setup
Education Cloud (EDA — Education Data Architecture) setup: student success hub, advisor workflows, enrollment management, academic data model. NOT for standard Service Cloud case management (use service-cloud-core-setup). NOT for Nonprofit Cloud data model (use nonprofit-cloud-vs-npsp-migration).
Best use case
education-cloud-eda-setup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Education Cloud (EDA — Education Data Architecture) setup: student success hub, advisor workflows, enrollment management, academic data model. NOT for standard Service Cloud case management (use service-cloud-core-setup). NOT for Nonprofit Cloud data model (use nonprofit-cloud-vs-npsp-migration).
Teams using education-cloud-eda-setup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/education-cloud-eda-setup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How education-cloud-eda-setup Compares
| Feature / Agent | education-cloud-eda-setup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Education Cloud (EDA — Education Data Architecture) setup: student success hub, advisor workflows, enrollment management, academic data model. NOT for standard Service Cloud case management (use service-cloud-core-setup). NOT for Nonprofit Cloud data model (use nonprofit-cloud-vs-npsp-migration).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Education Cloud EDA Setup Activate when configuring Salesforce Education Cloud / EDA for a school, university, or other learning institution. EDA is a contact-centric data model layered on standard objects, wired to the Student Success Hub and Advisor Link applications. Getting the foundational records (Account record types, Affiliations, Program Plans) right on day one prevents years of downstream reporting pain. ## Before Starting - **Confirm EDA package version.** Education Cloud features and Student Success Hub assume a minimum EDA version; a stale managed package will leave fields and triggers missing. - **Decide the Account model.** EDA uses FOUR Account record types: Academic Program, Household, Business Organization, Administrative. You must pick the model before any Contact load — Account defaults are used by the EDA triggers for auto-creation. - **Know the academic cadence.** Term/Course/Course Offering/Course Connection modeling depends on whether the institution runs semesters, trimesters, quarters, or rolling enrollment. ## Core Concepts ### Contact-centric model In EDA, the Contact is the primary record. Students, advisors, parents, faculty, and staff are all Contacts with different Affiliations. A Contact can have many Account relationships through `Affiliation__c`, including Primary Academic, Primary Business, Household, and Sports affiliations. ### Program Plan / Plan Requirement Academic programs are modeled as `Program_Plan__c` records with nested `Plan_Requirement__c` children. This is how EDA expresses "to graduate, a student must complete these courses." Advisor Link uses this structure to generate checklists. ### Term / Course / Course Offering / Course Connection `Term__c` defines the academic period. `Course__c` is the catalog-level record. `Course_Offering__c` is a specific instance of a course in a specific Term. `Course_Connection__c` links a Contact (student or faculty) to a `Course_Offering__c`. This is a four-level model and all four are required; skipping the split breaks Advisor Link reports. ## Common Patterns ### Pattern: Applicant to student conversion Represent applicants as `Contact` with `Affiliation__c.Status = 'Prospect'` to the target Academic Program. On admission, flip `Status = 'Current'` and add the Primary Academic Account. Do NOT create a separate `Applicant__c` custom object — it breaks Advisor Link assumptions. ### Pattern: Term rollover At term-end, `Course_Connection__c` records carry grades. Do not delete them — new connections for the next term are net-new inserts. A term-rollover Flow creates next-term `Course_Offering__c` records from the catalog `Course__c` and pulls forward enrolled students. ### Pattern: Advisor caseload Advisors have a `Caseload__c` junction to Contacts. Sharing on Contact respects the Household + Academic hierarchy; advisors are given Caseload-based sharing through an Apex-managed sharing trigger or criteria-based rules. ## Decision Guidance | Situation | Recommended Approach | Reason | |---|---|---| | New program launch | Program_Plan + Plan_Requirement tree | Advisor Link discovers programs this way | | Multi-campus institution | Separate Academic Program Accounts per campus | Enables reporting by campus | | K-12 vs higher-ed | Same EDA model, different record type usage | Avoid forking the schema | | Alumni engagement | Keep Contact + Affiliation Status = 'Former' | Preserves history without deleting | ## Recommended Workflow 1. Verify EDA managed package is installed and at the supported version; review release notes for upgrade-impacting trigger changes. 2. Activate the four Account record types and set defaults for auto-Household creation (EDA Settings → Accounts). 3. Configure Affiliation mappings: Primary Academic, Primary Business, Household — these drive auto-population on Contact. 4. Load Academic Program Accounts and Program Plans before any student data. 5. Import Contacts with a staged ETL: prospects → admitted → enrolled; each stage triggers Affiliation changes that EDA automation expects. 6. Set up Term, Course, Course Offering, Course Connection objects; deploy a term-rollover Flow before the first term-end. 7. Install Student Success Hub / Advisor Link apps, configure caseload sharing, and run a round-trip advisor check. ## Review Checklist - [ ] Four Account record types active and default behavior verified - [ ] Affiliation settings mapped to correct primary types - [ ] Program Plan + Plan Requirement hierarchy created for every active program - [ ] Term rollover automation in place before first term boundary - [ ] Advisor caseload sharing resolves to expected Contact set for a test advisor - [ ] Field History tracking on Affiliation Status (audit trail for FERPA) - [ ] Guest user hardening on any applicant-facing Experience Cloud portal ## Salesforce-Specific Gotchas 1. **EDA triggers run on Contact insert.** A bulk Contact load without the Primary Academic Account resolved in advance creates orphan Affiliations that advisors cannot see. 2. **`Course_Connection__c` is the grade holder.** Copying prior-term grades to `Course_Offering__c` is a common LLM mistake; grade history lives only on Course Connection. 3. **Household Account auto-creation is irreversible at scale.** Once EDA creates Household accounts for a Contact batch, turning it off does not tear them down — test on a sandbox sample first. ## Output Artifacts | Artifact | Description | |---|---| | EDA activation runbook | Ordered steps, package version gate, record type plan | | Term rollover Flow | Automates course offering generation each term | | Affiliation mapping table | Institution-specific Primary Account mapping | | Advisor caseload sharing spec | Apex-managed or criteria-based sharing rules | ## Related Skills - `admin/experience-cloud-site-setup` — student/applicant portal - `admin/nonprofit-cloud-vs-npsp-migration` — sibling industry model context - `data/eda-data-model-and-patterns` — data loader patterns for EDA - `security/experience-cloud-guest-user-hardening` — applicant portal safety
Related Skills
shield-kms-byok-setup
Configure Shield Platform Encryption with customer-supplied (BYOK) or customer-held (Cache-Only Key Service) tenant secrets, rotate them, and recover. NOT for Classic Encryption or field masking.
experience-cloud-security
Use when configuring access controls, sharing, or site security for authenticated or guest Experience Cloud (community) users: external OWD, Sharing Sets, Share Groups, CSP, clickjack protection, guest user record access. NOT for internal sharing model configuration (use sharing-and-visibility).
headless-experience-cloud
Use when building custom frontends (React, Vue, mobile, static sites) that consume Salesforce CMS content via the Connect REST API headless delivery endpoint. Triggers: 'headless Salesforce CMS', 'deliver CMS content to external frontend', 'React app Salesforce content API', 'custom frontend Experience Cloud data', 'CMS delivery channel API'. NOT for standard Experience Builder site development. NOT for CMS Connect (3rd-party CMS federation into Experience Builder). NOT for Experience Cloud LWC components rendered inside a site.
experience-cloud-search-customization
Use this skill when configuring or extending search on an Experience Cloud site — covering Search Manager scope configuration, LWR vs Aura search component selection, federated search setup, guest user search access, and custom search result components. NOT for SOSL/SOQL query development. NOT for internal Salesforce global search or Einstein Search for agents.
experience-cloud-multi-idp-sso
Use this skill when configuring multiple identity providers (OIDC and/or SAML) on a single Experience Cloud site or across tenant-specific portals in the same org — covering auth provider registration, Start SSO URL routing, Federation ID mapping, RegistrationHandler implementation, and simultaneous SP+IdP topology. Trigger keywords: multiple identity providers Experience Cloud, multi-tenant SSO community portal, vendor and citizen portal same site, OIDC SAML both on login page, tenant-specific login routing community. NOT for internal Salesforce employee SSO configuration. NOT for single auth provider setups — see experience-cloud-authentication for basic SSO.
experience-cloud-lwc-components
Use when building custom LWC components for Experience Cloud (Experience Builder sites, LWR portals, Aura-based communities). Covers community context imports, guest user Apex access patterns, navigation API differences between LWR and Aura, and JS-meta.xml target configuration for Experience Builder exposure. NOT for internal LWC components deployed to Lightning App Builder or standard record pages (see lwc/lwc-development). NOT for Aura community components. Trigger keywords: build LWC for Experience Cloud, custom component community portal LWC, guest user LWC component, community context import salesforce, lightningCommunity target, @salesforce/community, guest Apex.
experience-cloud-authentication
Use when building custom login pages, social SSO flows, self-registration flows, or passwordless OTP login for Experience Cloud (community) sites. Trigger keywords: custom login page Experience Cloud, social SSO community portal, passwordless login Experience Cloud, self-registration custom flow, headless authentication community, auth provider OIDC SAML site. NOT for internal SSO configuration (use identity/sso skills). NOT for standard username/password authentication with no customization.
experience-cloud-api-access
Use this skill when configuring or troubleshooting API access for Experience Cloud external users and guest users: guest user Apex data access, Customer Community Plus or Partner Community REST/SOAP API access, external user OAuth scopes, and sharing enforcement on API responses. Trigger keywords: Experience Cloud API access external user, community user REST API, guest user API limits, Customer Community API permissions, external user OAuth. NOT for internal Salesforce API authentication, non-community OAuth flows, or internal user API security.
slack-salesforce-integration-setup
Use this skill when setting up or troubleshooting the Salesforce for Slack managed app — including connecting a Salesforce org to a Slack workspace, configuring the three-party admin handshake, linking Slack channels to Salesforce records, enabling record preview sharing, and managing org-level limits. Triggers on: Salesforce for Slack app not connecting, Slack org connection setup, Salesforce record sharing in Slack, Slack workspace admin approval, connecting Salesforce to Slack. NOT for building custom Slack apps or Slack bots (separate development platform), not for Slack Workflow Builder Salesforce connector (use slack-workflow-builder skill), not for Flow-based Slack messaging (use flow-for-slack skill).
salesforce-maps-setup
Use when configuring Salesforce Maps (formerly MapAnything) — territory planning, route optimization, live tracking, geo-grid visualizations, and check-in/check-out workflows for Sales or Service field reps not on Field Service. Covers package installation order (Maps + Maps Advanced + Maps Routing/Live Tracking add-ons), the MapsTerritoryPlan / MapsAdvancedRoute / MapsLayer object family, base-data syncs (Geocoding and Routing services), and integration with Sales and Service Cloud records. Triggers: 'Salesforce Maps setup', 'MapAnything migration', 'territory planning by polygon', 'route optimization for sales reps', 'live tracking field reps', 'plot accounts on a map', 'check-in to the closest account'. NOT for Field Service Lightning territory and scheduling (use admin/fsl-scheduling-optimization-design and data/fsl-territory-data-setup) — Maps and FSL are different products. NOT for Consumer Goods Cloud retail visit planning (use admin/consumer-goods-cloud-setup) — RoutePlan/Visit objects are CG-specific. NOT for Tableau / CRM Analytics geo charts.
private-connect-setup
Configure Private Connect between Salesforce and AWS/Azure for traffic to stay on private networks. NOT for standard internet callouts.
net-zero-cloud-setup
Use this skill when configuring Salesforce Net Zero Cloud — including Scope 1/2/3 emission source modeling via the StnryAssetCrbnFtprnt / VehicleAssetCrbnFtprnt / Scope3CrbnFtprnt object families, emission factor library setup (EmssnFctr / EmssnFctrSet), DPE-driven carbon calculation jobs, supplier engagement scoring, and CSRD / ESRS / TCFD disclosure pack mapping. Triggers on: Net Zero Cloud setup, Sustainability Cloud carbon accounting, Scope 1 2 3 emissions Salesforce, emission factor library, supplier engagement Net Zero, ESG disclosure pack mapping. NOT for ESG content scoring (use Marketing Cloud), NOT for general financial reporting (use Accounting Subledger), NOT for energy-only utility billing (use Energy & Utilities Cloud).