/education-cloud-multi-campus-configure

name: education-cloud-multi-campus-configure
description: "Use this skill when a Salesforce Administrator needs to create OR maintain an institutional hierarchy for Education Cloud by parsing organizational structure from a PDF, URL, text, or CSV. On a first run it creates System, Campus, College, and Department Account records linked via ParentId plus 1:1 Business Profile records. On later runs it reconciles the org's existing hierarchy against the desired structure and applies only the delta — adding new units, renaming, or moving a node under a different parent — never recreating what exists. TRIGGER when the user wants to set up, configure, build, update, restructure, or reorganize a multi-campus structure, institutional hierarchy, or account hierarchy with business profiles; or add, rename, or move a campus, college, or department. DO NOT TRIGGER for single-campus flat setups without hierarchy levels, one-off manual account creation, or non-Education-Cloud account management."
metadata:
  version: "1.0"
  minApiVersion: "65.0"
  domains:
    - "Education"
  relatedSkills:
    - "education-cloud-domain-configure"
  accessCheck:
    - type: "license"
      value: "Education Cloud"
  mcpTools:
    headless-360:
      tools: ["describe", "discover", "dispatch", "dispatch_readonly"]
      semver: ">=1.0.0"
  cliTools:
    - tool: ["sf"]
      semver: ">=2.0.0"
allowed-tools: |
  Read AskUserQuestion Bash
  mcp__headless-360__discover
  mcp__headless-360__describe
  mcp__headless-360__dispatch
  mcp__headless-360__dispatch_readonly

Education Cloud Multi-Campus Institutional Hierarchy Configuration

Guides Salesforce Administrators through the full lifecycle of an institutional hierarchy: initial creation AND ongoing maintenance. Parses organizational structure from documents, URLs, CSV, or text, then either builds the hierarchy from scratch or reconciles it against what already exists in the org — creating only the delta. Supports any number of hierarchy levels (e.g., System → Campus → College → Department, or System → Region → Campus → Division → Department) based on the input. Creates/updates Account records with parent-child relationships and Business Profiles for each level, derives materialized paths on the fly for semantic navigation, and validates the result.

Mechanism

Try **`headless-360`** first for every Account/BusinessProfile read or write — reads via `dispatch_readonly`, writes via `dispatch` (see `references/mcp-invocation.md` for call shape, response envelope, and per-step invocations). Probe with `GET /services/data/vXX.0/limits` before the first call: 2xx → route everything through it. Absent/4xx/5xx → probe other available transports (another Salesforce MCP server, or authenticated `sf` CLI) with the same read, use the first healthy one, and tell the user which transport is in use. None healthy → stop, ask the user to connect one; never fabricate a result.

Scope

• **In scope**: Parsing institutional structure from PDF/URL/text/CSV with any number of hierarchy levels (2+); **new setup** (create full hierarchy); **update/reconcile** (compare desired structure to the org's current hierarchy and apply only the delta — add new nodes, rename a node, move a node under a different parent); creating Account hierarchy with parent-child relationships via ParentId; generating Business Profiles for all levels; deriving materialized paths on demand from the parent chain; validating parent-child relationships; handling API errors during bulk create/update
• **Out of scope**: Deleting Account or Business Profile records (destructive — report extras, do not delete unless the user explicitly confirms per Step 7); single-level flat structures (no parent-child relationships); non-Education-Cloud account management; migrating field data between hierarchy nodes

---

Required Inputs

Gather or infer before proceeding:

• **Organizational structure source** (the *desired* structure): PDF document path, website URL, CSV, or plain text description
• **System name**: Top-level institutional system name (e.g., "Riverside Community College System")
• **Hierarchy levels**: All organizational levels present (Campus, College, Department, Division, Region, etc.) — infer from parsing, do not assume a fixed 4-level structure
• **Mode hint** (optional): Whether this is a first-time build or an update to an existing hierarchy. If not stated, detect in Step 4.
• **Existing root** (update mode only): The System (root) Account Id, so the current hierarchy can be traversed. A prior run of this skill prints this Id in its summary (Step 10).

Defaults unless specified:

• Record type for all accounts: resolve from org (do not hardcode) — see Step 3.5
• Business Profile creation: Enabled for every hierarchy level that lacks one
• Materialized path: Not a stored field — derived on the fly by walking the Account's ParentId chain to the System root when displaying a path
• Naming convention: Title Case with spaces preserved
• Deletion: Never automatic — extra nodes in the org are reported, not removed

If the user provides a complete hierarchy description or document, parse and confirm the structure before creating or changing records.

---

Workflow

All steps are sequential. Do not skip or reorder. If blocked, stop and ask for missing context.

0. **Verify foundation prerequisites** — Follow `references/foundation_prerequisites.md`: org edition, Lightning Experience, Education Cloud license, running user's Full Access assignment, Education Cloud Foundation enabled (self-heal via confirm-then-enable if off). Do not proceed to Step 1 until all checks pass.

1. **Understand input format**

• Ask user for organizational structure source: PDF path, URL, CSV, or text description
• If PDF: use Read tool to extract text content
• If CSV: read columns `Name,LevelType,Level,ParentName` (see `examples/sample_hierarchy_input.csv` for the expected shape; `examples/sample_hierarchy_input_edgeca