Journey Map Builder: Permissions Guide

Published on November 13, 2026 User Journey Map Builder


Journey Map Builder: Permissions Guide

Audience: Salesforce administrators who install Journey Map Builder
Time needed: about 10 minutes

1. What the Package Uses

ObjectAPI NameUsed For
Journey Mappscjmb__Journey_Map__cThe map itself: name, persona, scenario/objective
Journey Map Phasepscjmb__Journey_Map_Phase__cThe steps of the journey: name, order, emotion, user actions, touchpoints, pain points, possible solutions

Journey Map Phase is a child of Journey Map through a Master-Detail relationship.

  1. Phases inherit sharing from their map, and a user who can't see a map can't see its phases.
  2. Phases can't exist without a map.
  3. Deleting a map deletes all of its phases.

2. Included Permission Set

Permission SetJourney MapJourney Map Phase
Journey Map Builder_AdminCreate, Read, Edit, DeleteCreate, Read, Edit, Delete
Assign this to anyone who builds and maintains journey maps.

3. What Each Action Needs

User ActionJourney MapJourney Map Phase
View a map in the Table or StoryboardReadRead
Use "Edit journey" (any editing)ReadRead, plus Create / Edit / Delete as needed
Edit map details (name, persona, scenario)EditRead
Add / duplicate a phaseReadCreate
Edit a phase, reorder phasesReadEdit
Delete a phaseReadDelete
Create a new journey mapCreateRead
Delete a whole mapDeleteDelete (phases are removed with it)

The Storyboard shows the "Edit journey" button only to users who can create or edit. Each action inside it is also gated by the user's access.

  1. Without Create, there is no "Add phase" or "Duplicate".
  2. Without Delete, there is no "Delete" button.
  3. Without Edit, the user can't save changes or reorder phases.

4. Assign the Included Permission Set

  1. Go to Setup > Permission Sets and open Journey Map Builder_Admin.
  2. Click Manage Assignments > Add Assignments.
  3. Select the users and click Assign, then Done.

5. Recommended: Create a Read-Only Permission Set

Many people only need to view maps. A separate set is cleaner than giving everyone full access.
  1. Setup > Permission Sets > New. Label it "Journey Map Builder_Viewer".
  2. Open Object Settings and, for Journey Maps and Journey Map Phases, check Read only.
  3. Under Field Permissions, grant Read on every field.
  4. Save and assign it to viewers.
Optional: an editor set. Clone the Viewer set and add Create, Edit and Delete on both objects, with Read and Edit on all fields. Use this when you want editors without the full admin set.

6. Check Field Access

Rich-text fields only show data if the user has field access. Confirm that each profile or permission set has Read, and Edit for editors, on:

  1. Journey Map Phase: Name, Order, Emotion, User Actions, Touchpoints, Pain Points, Possible Solutions
  2. Journey Map: Name, Persona, Scenario/Objective
A missing field shows up as an empty section, a missing label, or a save error.

7. Sharing (Who Can See Which Maps)

  1. Check the Organization-Wide Default for Journey Map. If it is Private, users only see maps they own or that are shared with them.
  2. Phases follow the map. Record access on a phase comes from its map.
  3. To widen access, use sharing rules, roles, or manual sharing on the map.

8. Test Checklist

Log in as a test user, or use Login As, for each permission set:

  1. Viewer can open a map and see every phase, but sees no "Edit journey" button.
  2. Editor can edit a phase and click Save phase without errors.
  3. Editor can add, reorder and duplicate phases.
  4. Deleting a phase works only for users with Delete.
  5. Editing Persona in "Edit map details" saves correctly. Persona is required.

9. Troubleshooting

SymptomLikely CauseFix
Map opens but no phases showNo Read on Journey Map Phase, or phase fields not readableGrant object Read and field Read
"Edit journey" button missingUser has no Create or Edit on either objectAssign the editor or admin set
"Add phase" missingNo Create on Journey Map PhaseGrant Create
Save fails with "insufficient access"Missing Edit on the object or a fieldGrant Edit and field Edit
Can't see a map others canSharing / org-wide defaultReview sharing settings
A section looks empty for one user onlyField-level accessCheck field permissions

Knowledge Article Number: KA-00502

View more articles in the knowledge base