Saphan StudioDocs
The console

Screens and routes

Every screen, its address, its sidebar group, and where its data comes from.

Every screen and its address

Every screen lives under /console/app/; the address below is the part after it. A plain /console opens Today. Simple and Advanced show the same screens — the mode changes their names and their detail, not whether they are there.

screen (Simple · Advanced)groupaddress
Today · Yours—today
Stuck · Refusals—stuck
AdvisorTalk torole-advisor
MasterTalk torole-master
Master — legs in flight(reached from Master)role-master/legs
ScribeTalk torole-scribe
Trains · Streams · trainsWorktrains
Runs · RunnersWorkruns
Source map · Source · mapWorksource
Pull requestsWorkpr
Event LogWorkevent-log
Bugs · Bug HarvesterWorkbugs
ReportsWorkreports
Prompts · Prompt LibraryWorkprompts
Agents · Fleet · seatsFleetfleet
DocumentsFleetdocuments
AuditFleetaudit
Sessions · Sessions · runsFleetsessions
Rules · PoliciesFleetpolicies
Costs · Ledger · CostsFleetledger
Ideas · SparksNotessparks
NotepadNotesnotepad
Settings(sidebar foot)settings
Verify the return(reached from Today)verify/<wagon>

Cast roles, reached from Settings → Seats, is drawn by the gateway's earlier pages, at /console/cast.

The sidebar is built from the console's one screen registry, so it cannot disagree with the screens that exist. An address the console does not know draws a screen that says so.

Where each screen's data comes from

A screen being drawn and a screen being fed are two different facts. Every screen above reads the record through the gateway, with these exceptions, each marked on the screen itself:

screen or partits data in this release
Settings → Fleet rules⚠ sample data; a change is refused, nothing is sent
Settings → System controls⚠ sample data; a change is refused, nothing is sent
Rules → People⚠ empty: no reader for the people register
Reports, a part of a plate this build does not answersays Not answered on this build — never a zero
The bottom panel's Train and Files tabs⚠ empty

Where a single value the record does not yet serve is filled from sample data, Advanced outlines it with a dashed amber line. Signatures and their verification, counts that drive acts, and money with a billing class are never filled from sample data — the screen draws — instead.

The previous console

Two other consoles can answer on a machine, and the pages at the end of this section describe the first of them:

  • The projection server's console (saphan server start, or the saphan-server daemon), with its queue, its decision form and its terminal endpoint — see Signing in and the pages after it.
  • The gateway's earlier, server-rendered pages. By default every old screen address on the gateway, /console/<screen>, redirects to /console/app/<screen>. An operator can serve the old pages again by setting legacy = true in the [console] section of the configuration file (saphan config set console.legacy true); absence, false and an unreadable configuration all keep them out. Screens the old pages draw and this console does not — Cast roles, for example — stay served either way.

On this page