Saving & Versioning

Saving

The wizard tracks unsaved changes with dirty state detection. Save your work at any time using the Save button in the wizard header or the keyboard shortcut Ctrl+S. If you try to navigate away with unsaved changes, you'll see a warning.

Undo & Redo

The wizard maintains a full change history within each session. Use the undo and redo buttons in the toolbar to step through your recent changes. A history panel shows the timeline of actions.

Copying a matrix

You can copy an entire matrix configuration from one project to another, even across different hubs. This is useful when setting up new projects that should follow the same structure as an existing one.

What gets copied

• Level values — All L1, L2, and L3 values with descriptions.
• Overrides — Per-party L2/L3 restrictions.
• Display names — L1 party label mappings.
• Folder structure — Templates, exclusions, renames, and expansion toggles.
• Permissions — All folder-to-role permission assignments.
• Role groups — Group definitions with child roles and match modes.

What is not copied

• Access request forms — These are project-specific and must be set up separately.
• Deployed state — Folders and permissions need to be deployed to the new project.

Multiple configurations

A single project can have multiple matrix configurations — for example, for different phases or scenarios. When building an access request form, you select which configuration to use from a dropdown. The most recently updated config is shown with a star indicator.

Deleting a matrix

Removing a matrix configuration cascade-deletes all its child records: level items, overrides, display names, folder paths, folder permissions, and role groups.