Sources
Docs: Preferences and Policies Web App: A Pane’s controls save a setting for you or, when the Pane offers it, for the whole Workspace.Story
A setting belongs to exactly one owner: the person who saved it, or the Workspace.
The app’s own defaults are not a scope. They are part of the app’s definition —
the Pane’s code and Perception — and are versioned with the Parable like every
other edit.
Only people and Workspaces own settings. An agent acting for you saves settings
as you.
Choose between them
Parable does not fall back from a person’s setting to the Workspace’s, or from either to the app’s default. A Pane that offers both reads both and decides which to show. Clearing your own setting shows the Workspace’s only when the Pane’s code does that. A Live setting is not part of a Version: publishing does not copy, reset, or roll it back. A Versioned setting is part of each Version and changes only through one, so it has no Me scope (Live or Versioned).Who may write where
- Your own setting: you, from a Pane that offers a control for it. Nobody else can read or change it.
- The Workspace’s setting:
create.preferencespermits its first save,edit.preferencespermits replacing it, anddelete.preferencespermits deleting it. The Pane’s current Policies on the line decide each action; an older Version’s Policies do not grant access. - The app’s defaults: the authoring save, under the Parable’s participants and the Pane’s Policies, like every other edit.