Guided Journey Repository

Overview

The Guided Journey Repository is a content library built into the CloudShare Editor that lets content authors save, reuse, and manage Guided Journeys across Experiences within a project.

Instead of rebuilding a Guided Journey from scratch for every new Experience, or duplicating and editing an existing one, authors can save any GJ to the repository and load it into another Experience in a single click.

When a GJ is saved to the repository, it's stored as a standalone independent copy. Editing the original GJ afterward has no effect on the saved entry, and loading a GJ from the repository creates a new independent copy in the Experience with no ongoing link back to the source. This means repository entries are always a snapshot in time of the content as it was when saved, not a live, syncing reference.

Note: The Guided Journey Repository is scoped to the project. All Guided Journeys saved to the repository are available across every Experience within that project.

Loading a Guided Journey from the Repository

When no Guided Journey is currently loaded in an Experience, an entry point to the repository appears in the Add content menu ("+"):

• Read permission users see Load from Repository.
• Write permission users see Manage Repository instead, which opens the same browsing list with additional management options (see Renaming and Deleting a Guided Journey).

To load a Guided Journey from the repository:

1. With no Guided Journey loaded, click the Add content ("+") menu.
2. Select Import from Repository (or Manage Repository if you have write permission).
3. The panel opens to Browse Guided Journeys: a table of saved Guided Journeys for the project, with Name and Added Date columns.
4. Use the search box above the table to find a specific Guided Journey. As you type, the list filters in real time to show only matching entries.
5. If the repository has more entries than fit on one page, use the page indicator ("Page X of Y") and the arrow controls beside it to move between pages.
6. Click the import icon next to the Guided Journey you want to use.

The Guided Journey loads into the Experience immediately as an independent copy. Since nothing is currently loaded, there's nothing to overwrite, so no confirmation dialog appears and the panel closes automatically.

Note: Loading from the repository is available to every authenticated user, regardless of permission level.
Read permission is enough to browse and import; only adding, renaming, and deleting require write permission.

Note: If the repository doesn't contain any entries yet, the panel still opens, showing an empty state instead of a list. The entry point to the repository is always available, even before your first Guided Journey has been saved.

Note: You can also click the Name column header to sort the list alphabetically. By default, entries are ordered newest first by Added Date.

Saving a Guided Journey to the Repository

Saving to the repository requires write permission. When a Guided Journey is loaded in the Experience, write permission users see a Manage Repository option in the Guided Journey's context menu ("...").

To save a Guided Journey to the repository:

1. With a Guided Journey loaded, open the Guided Journey's context menu ("...") and select Manage Repository.
2. The panel opens with an Add to Repository section at the top: a name field ("Create a new repository item or choose an existing one to replace") and an Add button. The Browse Guided Journeys list appears below it, with the same search box and pagination described in Loading a Guided Journey from the Repository.
3. Type a name for the Guided Journey in the field. The Add button stays disabled until a name is entered.
4. Click Add.

If the name you entered doesn't match any existing entry, the Guided Journey is saved as a new repository entry right away.

Overwriting a Pre-Existing Guided Journey

If the name you type in the Add to Repository field exactly matches an existing repository entry, clicking Add triggers a confirmation dialog:

Overwrite Guided Journey? "You are about to overwrite [Existing GJ Name] with your current Guided Journey. This action cannot be undone."

• Clicking Overwrite replaces the previous entry entirely with the current Guided Journey. There's no version history, so the previous content can't be recovered once confirmed.
• Clicking Cancel returns you to the Add to Repository field so you can enter a different name.

Note: A saved repository entry always reflects the Guided Journey exactly as it was at the moment you clicked Add. If you keep editing the Guided Journey in the Editor afterward, those changes are not automatically reflected in the repository, you'll need to save again to update the entry.

Renaming and Deleting a Guided Journey

Renaming and deleting are available to write permission users from the Browse Guided Journeys list, whether it was opened via Load from Repository/Manage Repository (no Guided Journey loaded) or via the Guided Journey context menu's Manage Repository (Guided Journey loaded). Both use the ⋮ menu next to any repository entry.

Renaming a Guided Journey

1. Click the ⋮ menu next to the entry and select Rename.
2. The entry's name becomes an editable text field directly in the list, no dialog is shown.
3. Type the new name.
   • Press Enter to confirm and save the new name.
   • Press Escape, or click outside the field, to cancel and restore the original name.
4. If the name you enter already exists in the repository, an inline error appears: "Name already exists. Choose a different one." The rename can't be confirmed until the name is unique.

Renaming only changes the entry's name. The content and creation date are unaffected.

Deleting a Guided Journey

1. Click the ⋮ menu next to the entry and select Delete.
2. A confirmation dialog appears: Delete Guided Journey? "You are about to permanently delete [GJ Name]. This action cannot be undone and it will be removed from your repository."
3. Click Delete to confirm, or Cancel to keep the entry.

Note: Deleting a repository entry only removes it from the repository. If that Guided Journey was already loaded into an Experience at some point, the loaded copy in that Experience is unaffected.

Permission Management

Access to the Guided Journey Repository is split into two levels:

Account Managers always have full write access to the repository, regardless of their own permission checkbox state.

Granting write access:

Write access is granted per project, not account-wide. A user can have write access in one project and not in another.

1. As an Account Manager, open the User Details page for the relevant user and select Change User Level.
2. In the Change User Level dialog, select the project you want to change the user's access for.
3. Locate the Permissions section and the Manage Guided Journey repository checkbox.
4. Check the box to grant write access for that project, or uncheck it to revoke it.
5. Confirm the dialog. The user level and the repository permission for that project are saved together in a single action.

Repeat the process for each additional project where you want to grant or revoke this user's write access.

The current permission state for a project is also visible as a read-only checkbox in the Permissions row at the bottom of the User Details page, so you can check a user's access without opening the edit dialog.

Note: Loading from the repository doesn't require any specific permission; it's available to all authenticated users. Only saving, renaming, and deleting are gated behind the Manage Guided Journey repository permission.