---
schema_version: "1"
id: 9e9317f7a30ffdc27fd69749a2d6bcb10f4b3934523683944ac0988ed08779f7
title: Configure Planning Hierarchies in Marketing Planning and Operations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mktg_pln_oper_hierarchy_create.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mktg_pln_oper_hierarchy_create.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 13a33abb2bdf1edb14ceac59de5fdce599baf8a3d714967f37dd5ef380d1cdbc
description: Configure the planning hierarchy tiers that your marketing teams use to organize and track work. Define the tiers that connect executive objectives to executable plans, and then assign those tiers to hierarchy groups. Create multiple groups when different teams need different hierarchy structures.
products:
- Marketing
release: "264"
---
# Configure Planning Hierarchies in Marketing Planning and Operations
Configure the planning hierarchy tiers that your marketing teams use to organize and track work. Define the tiers that connect executive objectives to executable plans, and then assign those tiers to hierarchy groups. Create multiple groups when different teams need different hierarchy structures.
### Required Editions
Setting up planning hierarchies is a two-step process. First, you define individual hierarchy nodes, such as Business Objective, Initiative, or Plan. Each node sits at a tier, where the tier is the level in the hierarchy: Tier 1 is the broadest scope, and deeper tiers get more specific. More than one node can sit at the same tier, giving you the flexibility to build different structures for different teams.
Second, you create hierarchy groups that determine which nodes each team uses. Each group picks one node per tier to create a complete rollup structure. Skip-level relationships help marketing programs to bypass intermediate nodes and connect directly to higher-level parents. This flexibility helps when work doesn't fit a full cascade.
Here's an example showing both steps for two different team structures:
Corporate Marketing Hierarchy
| Node | Tier | Skip-Level Parent |
| --- | --- | --- |
| Business Objective | 1 | None |
| Marketing Directive | 2 | None |
| Initiative | 3 | None |
| Program | 4 | None |
| Plan | 5 | Marketing Directive |
Regional Marketing Hierarchy
| Node | Tier | Skip-Level Parent |
| --- | --- | --- |
| Regional Objective | 1 | None |
| Product Initiative | 2 | None |
| Go-to-Market Program | 3 | Regional Objective |
In this example, a plan in the Corporate Marketing Hierarchy can roll up to either a program or skip directly to a marketing directive. A go-to-market program in the Regional Marketing Hierarchy can roll up to either a product initiative or skip directly to a regional objective.
## Create Hierarchy Nodes
1. From Setup, use the Quick Find box to find and select **Marketing Planning Hierarchy**.
2. On Hierarchy Tiers, click **Add First Node**.
3. Enter the node name and its tier.
4. Save the node.
5. To add subsequent nodes, click **Add Node**.
## Create Hierarchy Groups
1. Go to **Hierarchy Groups**.
2. Click **Create First Group**.
3. Enter the name and description of the planning group.
4. Click **Add First Node**.
5. Select and add the first node of the hierarchy group.
6. To add subsequent nodes, click **Add Node**.
The group orders nodes automatically by tier.
7. To configure skip-level relationships for a node:
1. From the Allowed Parents column, click 
2. Select and add the node that you want to allow as a parent of the current node.
8. To control who can create programs at a node:
1. From the Creators column, click 
2. Select and add a user, a public group, or a profile that you want to add as a creator of the current node.
Add up to five creators to a node. If a node has no creators, anyone with permission to create marketing programs can create them at that node. Adding an allowed creator grants permission only to create marketing programs at that node. It doesn't grant permission to view, edit, or delete the programs at that node.
9. After the hierarchy group is ready, activate it.
Leaders and marketing teams can add work only to active hierarchy groups.