Salesforce Docs Portal

Multi-Campus Institutional Hierarchy Configuration with AI Tools

A guided session builds a multi-campus account hierarchy that represents your institution's system, campuses, colleges, and departments. When you describe your campus structure or provide a source document to a coding agent, the agent analyzes the source and creates the account hierarchy. This foundation supports enrollment, reporting, and role-based access.

Required Editions

Available in: Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions with Education Cloud

Scenario

A Salesforce admin wants to model the multi-campus system for your institution with its colleges and departments before teams configure enrollment and reporting. To avoid creating every account and linking records manually, the admin connects a coding agent to the Headless 360 MCP Server (Beta) and provides the catalog page as the source document. The agent reads the structure, proposes a hierarchy for approval, and creates the account records and business profiles with parent-child links. Later, the admin updates the hierarchy by using the coding agent.

Note
Note Headless 360 MCP Server is a beta service that is subject to the Beta Services Terms at Agreements - Salesforce.com or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this beta service is at the Customer's sole discretion. For more information, see Headless 360 MCP Server (Beta).

Requirements

  • Education Cloud Full Access permission set. The agent checks for and assigns the required permission sets based on your privileges, so it never grants access that you don't have.
  • A coding agent, such as Agentforce Vibes or Claude Code, connected to the Headless 360 MCP Server (Beta) with access to Education Cloud setup skills. For Agentforce Vibes, no installation is required. Agentforce Vibes installs, enables, and updates AI Skills automatically. You can manage them from the Skills page, under Toolkit, in Agentforce Vibes. For Claude Code, install the Salesforce Development plugin, which provides Salesforce-specific skills and org context through hosted Model Context Protocol (MCP) servers.

Suggested Technology and Experience

Recommended for Salesforce admins who are comfortable with Setup and with running a coding agent against a connected org. No prior experience with a specific skill is required.

Agentic Tips

  • Describe your goal in your own words. For example:
    • "Help me set up our institutional hierarchy."
    • "Here's our website: https://www.example.com/about/campuses"
    • "We have a system with three campuses. Main Campus has a College of Engineering with Computer Science and Electrical Engineering departments."
    • "Show me the path for the English department."
  • Provide reliable sources. A structured spreadsheet or CSV file is more reliable than a website, which can return incomplete results. If you point the agent to a web page, instruct it to include every campus.
  • Approve each change. The agent proposes a hierarchy and pauses for your confirmation before creating or changing any record. Read operations require no approval. Create, update, and delete operations require your confirmation.
  • Avoid pasting credentials into a prompt. The agent acts as your authenticated user through the connected org.

Design Considerations

  • The agent builds and updates. Describe your goals again to add, rename, or move a campus, college, or department. The agent applies only the difference. Account names must be unique within their sibling group so the agent can match records reliably.
  • Deletions are deliberate. The agent never removes records automatically. It reports extra records and deletes one only with your confirmation. Deleting an account also removes its business profile and child accounts.
  • Institution type has a fixed set of values. The Business Profile Institution Type field is a managed, restricted picklist. For an institution that doesn't fit those values, capture the detail in the Description field.
  • Sharing rules are a manual step. Configure sharing rules for role-based access in Setup after the hierarchy exists.

Build Your Institutional Hierarchy with a Coding Agent

Describe your campus structure or point the coding agent to a source file. Then, the agent creates the account records and business profiles with parent-child links.

Required Editions

Available in: Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions with Education Cloud
User Permissions Needed  
To run setup skills through a coding agent: Education Cloud Full Access
Note
Note Headless 360 MCP Server is a beta service that is subject to the Beta Services Terms at Agreements - Salesforce.com or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this beta service is at the Customer's sole discretion.

Before you start:

Note
Note For Claude Code, install the Salesforce Development plugin, which provides Salesforce-specific skills and org context through hosted Model Context Protocol (MCP) servers.

Then, configure a multi-campus hierarchy.

  1. Instruct the agent to set up your institutional hierarchy, and provide your structure as a spreadsheet, web page, PDF, or description.
  2. Have the agent read the source and propose a hierarchy of your system, campuses, colleges, and departments.
  3. Review the proposed hierarchy. Approve it, or ask the agent to make changes.
  4. Have the agent create the account records and business profiles and link each child to its parent.
  5. Review the agent's summary of what it created, and confirm the hierarchy in Salesforce.
  6. To apply later changes, describe your updated structure to the agent and approve the differences it proposes.