forcedotcom/sf-skills / plugins/builder/education-cloud/skills/education-cloud-domain-configure
education-cloud-domain-configure
VerifiedUse this skill to configure Education Cloud domains (Student Success, Recruitment & Admissions, Academic Operations, Alumni Relations, Student Management, or Mentoring) through conversational setup. Triggers when a user wants to enable or configure Education Cloud features. Guides step-by-step: enables Person Accounts prerequisite, activates target domain, then configures domain sub-features. Covers support processes, case record types, success teams, care plans, applications, admissions, course catalog, alumni engagement, fundraising, enrollment, programs, and mentoring. Explains each feature, confirms before proceeding, verifies every change took effect, and warns that domain and feature toggles are IRREVERSIBLE. DO NOT TRIGGER for metadata generation, custom objects, or package deployment — this configures existing platform features via org settings, not metadata files.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.6 KB |
| references/dependent-features.md | markdown | 18.7 KB |
| references/domain-features.md | markdown | 3.3 KB |
| references/domain-features/academic-operations.md | markdown | 19.5 KB |
| references/domain-features/alumni-relations.md | markdown | 5.8 KB |
| references/domain-features/cross-domain-dependencies.md | markdown | 1014 B |
| references/domain-features/industriessettings-toggle-reference.md | markdown | 2.8 KB |
| references/domain-features/mentoring.md | markdown | 7.5 KB |
| references/domain-features/recruitment-admissions.md | markdown | 12.8 KB |
| references/domain-features/student-management.md | markdown | 5.7 KB |
| references/domain-features/student-success.md | markdown | 13.3 KB |
| references/gotchas-extended.md | markdown | 6.7 KB |
| references/setup-widgets.md | markdown | 8.7 KB |
| references/toggle-write-path.md | markdown | 6.3 KB |
| scripts/check_license_provisioned.pyexecutable | script | 2.0 KB |
| scripts/check_org_edition.pyexecutable | script | 1.4 KB |
| scripts/check_permission_assigned.pyexecutable | script | 1.1 KB |
references/gotchas-extended.md
View on GitHub# Additional Gotchas
Lower-frequency gotchas and toggle-write failure classes, split out of `SKILL.md`'s Gotchas table (kept to the 10 highest-impact entries). Read this when the top-10 table doesn't cover the error you're seeing.
| Issue | Resolution |
|-------|------------|
| Org edition not Enterprise+ | Education Cloud requires Enterprise, Performance, Unlimited, or Developer Edition — cannot install on lower editions |
| Some sub-features require additional licenses | If enablement fails with license error, inform user of required license (e.g., Salesforce Scheduler requires Field Service, Fundraising requires Advancement license, Experience Cloud license for portals) |
| Student Management has no separate domain toggle | Student Management is enabled when Academic Operations is configured with student enrollment records |
| Record creation (Business Process, Learning Programs) must be done manually or via API | Education Cloud does not auto-create these records — user must create via Setup, Data API, or Tooling API after domain is enabled |
| OmniStudio components must be activated separately | After OmniStudio is enabled, individual OmniScripts and FlexCards (Application Stages, Course Search, Matching Assessments) must be activated in Setup → OmniStudio |
| Experience Cloud portals require separate configuration | After domain is enabled, portals (Learner Portal, Applicant Portal, Alumni Portal, Mentoring Portal) must be created/configured in Experience Builder with domain-specific components |
| Sub-feature configuration steps vary significantly by domain | Always read the domain's file under `references/domain-features/` for domain-specific setup paths — Student Success, Recruitment & Admissions, and Academic Operations have 10+ sub-feature steps each |
| Verification queries may fail if objects not yet provisioned | Some domains provision objects asynchronously — retry after 2-3 minutes if query fails with "invalid object" error |
| `SELECT IsPersonAccountEnabled FROM Organization` returns `INVALID_FIELD` | No such column on `Organization` — verify Person Accounts via `Account/describe` (API, headless first) and check for `IsPersonAccount`/`Person*` fields, or `sf sobject describe -s Account` as fallback |
| Profile permissions on newly created RecordTypes (including LearningAchievement types) are NOT settable via API | Record type creates successfully but has no profile visibility — flag as a manual follow-up step (Setup → Profiles → Record Type Settings, or a `Profile` metadata deploy) |
| SOAP `updateMetadata` / `metadata/deployRequest` return `ROUTE_NOT_FOUND` | Blocked through the gateway — do NOT use; the headless metadata PUT is the supported write path (see "Endpoints that DO NOT work" in `SKILL.md`) |
| **Failure class — Aura-only, no MDAPI/Tooling/REST route at all** (e.g. Industries Cloud Common Decision Tables Access, `BREDecisionTableAccess`) | Backing call is an internal Aura action with no external route — manual UI only, do not keep probing endpoints |
| **Failure class — API write blocked at field level** (e.g. Intelligent Question Generation, `enableSmartAsmtQstnGeneration`) | Field exists and name is correct, but write returns `INSUFFICIENT_ACCESS_OR_READONLY: "cannot be accessed using the API"` — manual UI only |
| **Failure class — hard reject on disable-only** (e.g. Discovery Framework, `enableIndustriesAssessment`) | `true→false` returns HTTP 500 `UNKNOWN_EXCEPTION`; this is separate from the general one-way irreversibility — the enable (`false→true`) direction is untested where the field was already `true` |
| **Failure class — settings type invisible to Tooling/EntityDefinition but still MDAPI-writable** (e.g. Omnistudio Metadata, `OmniStudioSettings`, `fullName: OmniStudio`) | Metadata PUT write succeeds, but no GET/verify path exists via Tooling API — UI-confirmed only; if you encounter one of these, note it as write-succeeds-zero-verify-path rather than assuming failure |
| **Failure class — type-level UPDATE block** (e.g. Timeline `TimelineSettings`, Video Calls `VideoCallsSettings`) | PUT returns HTTP 400 `UNSUPPORTED_OPERATION: "MetadataCrud does not support UPDATE on type: X"` — block is on the whole type, no `fullName` variant fixes it; manual UI only |
| **Pattern — org preference API, not `IndustriesSettings`** (confirmed on Einstein Generative AI, `EinsteinGPTCopilotEnabled`) | Some toggles are Setup-Connect org preferences, not `IndustriesSettings` metadata fields — no `type`/`fullName`/`xmlRep`. Shape: `GET /services/data/v68.0/setup/org/preferences/<PrefName>` → `{"isPreferenceEnabled": bool}`; `PATCH` same path with `{"desiredState": true}` → response echoes post-write state. If a metadata PUT returns `FIELD_INTEGRITY_EXCEPTION: invalid at this location` for a plausible-looking element name, the field may not be on `IndustriesSettings` at all — try this org-preference path next before assuming manual-UI-only |
| **Failure class — write-enabled `dispatch` MCP tool not connected/loaded** | Fall back to the `sf api request rest` CLI (via Bash) for the exact same READ/WRITE/cold-VERIFY calls before giving up to manual Setup UI — confirmed working in the same run where other datasets hit this identical MCP gap. Never report a toggle's state as "assumed default" or "pending admin confirmation" without trying this fallback first |
## Transport call shapes
**SOQL routes via headless-360 — pass the query through `queryParams`, NOT inline `?q=` in `url`.** `GET /services/data/vXX.0/query` (or `/tooling/query`) with `queryParams: {"q": "SELECT ..."}` returns records normally; putting `?q=...` directly in the `url` string 404s (`ROUTE_NOT_FOUND`) — a call-shape mistake, not a platform limitation. `?fields=` on a plain sObject GET is still not supported (router treats it as an external-id path segment) — use `/describe` for field lists instead. Prefer a direct SOQL existence/Id lookup over asking the user to supply a record Id; where no REST route exists at all (license/permission provisioning UI-only), ask the user or confirm in Setup UI.
## Person Accounts verification
`GET /services/data/v68.0/sobjects/Account/describe` and confirm `IsPersonAccount`/`Person*` fields are present in the `fields` array; if headless routing is unavailable, fall back to `sf sobject describe -s Account` and grep for the same. This describe call is the ONLY valid verification method — do NOT run any SOQL query against `IsPersonAccount` or Person-Account fields (on `Account`, `Organization`, or any object) to check enablement status; SOQL on an unrecognized field returns `INVALID_FIELD`/"No such column", and that failure does NOT mean Person Accounts is off — it means you used the wrong check.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |