What this screen does
The Screen Map is a diagram of the application described by your specification: every screen as a node, arrows for navigation flows, and role annotations showing who can reach what. It is generated with the specification and stays attached to it as a version-controlled artifact.
Typical workflow
- Open the Screen Map tab on the Specification page.
- Read it like a floor plan: entry points (login, dashboard) on one side, then follow the arrows a given role would take to complete a task.
- Check each role's reachable screens — a role with access to too much or too little is the cheapest kind of bug to fix at this stage.
- If a screen or flow is missing, refine the boards (Solution shape and Operating model drive this diagram) and regenerate the specification.
- Download the screen map as JSON from the specification's download menu if you want to process it elsewhere.
Examples & tips
- The screen map is not just documentation: code generation uses it to build the generated app's navigation and role-based access. A screen missing here will be missing there.
- Right-click a node to ask the project agent about it — for example, "who approves an order on this screen?"
- Orphan screens (no arrows in) usually mean a flow was described but never connected; that is a board-level fix, not a diagram-level one.