Skip to main content

​
What are registry pages?

Registry pages are full screens your workspace subscribes to — purpose-built views that combine query configuration and visual layout. They live under the Visual Registry pillar of Intelligent Registries. Examples include people lists, business directories, operations dashboards, and marketing landing pages wired to live entity data.
Screenshot placeholder Pages catalog (/p): subscribed registry pages with titles, review status badges, and links to live pages.

​
Pages catalog

Open Intelligent Registries → Pages to see every page your organization subscribes to. Each entry shows:
  • Title and short description.
  • Page code — the URL segment used to open the page (e.g. /p/people-list).
  • Review status — whether the page has been marked as reviewed for your facility.
Click a row to open the live page or its configuration detail.
Screenshot placeholder Single registry page detail in admin (/p/[page-code]) showing title, query/render summary, and preview link.

​
How a page is built

Every registry page combines two concerns: App-level templates define defaults; your organization’s subscription can override titles, query tweaks, and render choices for your facility without forking the entire template.
Video placeholder (Screen Studio) Walkthrough: open Pages catalog → click a list page → show entity rows rendering → click into add-instance or detail flow if present on that page.

​
Common page patterns

Pages are not generic blank canvases — they assemble registered components that know how to talk to the Context Registry.

​
Subscriptions and review

Your workspace subscribes to pages published for your app. Subscriptions control:
  • Whether the page is visible in your catalog.
  • Facility-specific overrides (labels, empty states, filter defaults).
  • Review markers — pages pending review show until your team confirms they match production expectations.
Screenshot placeholder Page catalog row showing Reviewed checkmark vs Pending review dashed state.

​
Pages and Tracks

Registry pages and Tracks complement each other:
  • Pages expose registry data — browse people, open records, add instances.
  • Tracks run processes on those instances — checkpoints, milestones, overseers.
A people list page might be where recruiters discover candidates; a hiring track runs on the same people entity type defined in the Context Registry.

​
Pages vs. Entity Manager

Next: Components — building blocks pages assemble.