Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt

Use this file to discover all available pages before exploring further.

The journey editor is where Custory becomes operational. The controls matter because they decide whether the journey feels like a maintainable system or a diagram that is painful to update. This guide focuses on the controls that help smaller teams work quickly without losing structure.

​
The main control areas

Inside the editor, the most important controls are:
  • View switcher
  • Search
  • Filters
  • Visible properties
  • Undo and redo
  • Settings menu
  • Command menu
Use them together. The editor is designed for active maintenance, not just passive viewing.

​
Switch views based on the question

Custory supports multiple views over the same underlying journey. Use:
  • Journey view when you need the story in sequence
  • Grid view when you want grouped working lanes
  • Table view when you need bulk review and cleanup
  • Impact vs effort when you need prioritization
The key idea is that you are not creating separate versions of the journey. You are changing the lens. Use the search box at the top of the editor to narrow a large journey quickly. Search works across items and is designed for real working sessions, not only exact-title lookup. In practice, search combines:
  • Fast keyword matching
  • Semantic search support
That means you can often find relevant work even when you do not remember the exact wording.
  • Find all references to one recurring problem
  • Pull up a theme before a review
  • Narrow a large journey before cleanup
  • Locate an item quickly during a meeting

​
Filters

Use filters when you need to move from “everything in the journey” to “the subset we should discuss right now.” Common filters include:
  • Item group
  • Status
  • Owner
  • Priority
  • Impact
  • Effort
  • Stage or step context
The filter controls are especially useful for smaller teams because they let one shared journey support several different working modes instead of forcing separate artifacts.

​
Practical filter patterns

  • Filter to Opportunities before prioritization
  • Filter to one owner before a handoff review
  • Filter to high-priority work before planning
  • Filter to one step when a specific product moment needs attention

​
Visible properties

Use the property selector when you want the editor to show only the fields that matter for the current review. Examples:
  • Show Owner and Status during execution review
  • Show Impact, Effort, and Priority during prioritization
  • Hide less relevant fields to reduce noise
This is one of the easiest ways to make a large journey feel manageable.

​
Undo and redo

Custory supports editor-level undo and redo controls. Use them when:
  • You made a structural change too quickly
  • You want to back out of a cleanup pass
  • You are experimenting during a working session
Keyboard shortcuts:
  • Cmd/Ctrl + Z for undo
  • Cmd/Ctrl + Shift + Z for redo
  • Ctrl + Y can also work for redo on some systems

​
Settings menu

The editor menu gives you access to higher-level actions such as:
  • Journey settings
  • Version history
  • CSV export
Use these when you are moving from day-to-day editing into administration, auditing, or sharing work externally.

​
Export CSV

Use CSV export when you need a flat export of the current journey data for:
  • Offline review
  • Ad hoc analysis
  • Stakeholder handoff
  • Import into another reporting workflow
Export is useful, but it should not replace the live journey as the working source of truth.

​
Command menu

Custory includes a command menu for faster navigation and quick actions. Open it with:
  • Cmd + K on Mac
  • Ctrl + K on Windows/Linux
From the command menu, you can:
  • Search for items
  • Add a new item
  • Open AI chat
  • Open guide mode
This is especially useful during live review sessions when you want to move quickly without hunting through the UI.

​
Search-first workflow for small teams

A strong pattern during weekly review:
  1. Search for the theme you want to review
  2. Filter to the relevant group or owner
  3. Adjust visible properties
  4. Switch to the best view for that decision
That turns one large journey into a manageable working surface without duplicating work.

​
How to keep the editor usable as the journey grows

As your journey gets larger:
  • Use search before scrolling
  • Filter before bulk editing
  • Narrow visible properties before discussion
  • Switch views instead of forcing one view to do every job
The teams that struggle with large journeys usually try to work from the full surface at once.

​
Common mistakes

​
Staying in one view for every task

The editor is designed for lens switching. Use it.

​
Leaving every property visible

That creates visual noise and slows down review.

​
Treating search as exact-match only

It is useful for theme-finding, not just title lookup.

​
Doing large cleanup passes without filters

Always narrow the surface first.