Skip to main content

​
Reviewing app access

App Blueprint → Access is the visual map of who can reach what in your app blueprint. Open it after you add or change roles, pages, actions, or table access, and before you invite real users. Use it whenever Preview as a role fails in a surprising way. Access is read-only: it does not change permissions by itself. You fix permissions on Roles, Pages, Tools, and model access, then refresh Access.

​
How to verify

Work it like a short security review:
  1. Inventory roles under Roles.
  2. In Access, pick a role: nav, pages, tools, and tables they can reach.
  3. Check findings for common mistakes (actions hidden only by UI conditions, page actions that expose a restricted tool, table sources without model access).
  4. Use By Role, Matrix, and Graph tabs when the app is large.
  5. Preview as the same role and try a path that should fail.
  6. Fix permissions, then refresh Access and Preview again.
Example outcome check: the participant role should only reach My plan and the check-in. Nothing should expose staff actions or the library.

​
Limits and notes

  • Hiding a nav item is not the same as revoking page or tool access.
  • Builder (owner/admin) success is not proof a customer role can (or cannot) do the same.
  • Pair with Preview as a role and the Launch checklist.