Flowweaver examples
The recipients
This is the publisher's half. Recipients are set up once, by whoever runs the service — in the SiteVision module the list lives in the app's global settings. The editor then picks from the list while building the guide, and the visitor never sees it.
The catalog
Add recipients with a name and an address. The address stays here. The guide carries an id, and the picker in the editor sees names and ids — never addresses. That is the whole reason the catalog is a page of its own: it belongs to the system, not to the form.
One row is the default recipient — chosen in the row's ⋯ menu, like the published one in the versions list. Errands whose recipient has been removed from the list go there, so no report lands nowhere.
And then?
The editor’s choice and the visitor’s path are on Submissions and receipts: the same catalog, seen from the other two roles.