Sources
Docs: Collaboration and Participation Modes, Personal vs. Published Web App: Open People on a new composed Parable to see its participants.Story
A composed Parable starts Personal. Personal is not a mode you choose: it means only you so far, and you edit it directly. Edits save directly to the Parable. There is no Changes set to select or Version to publish as part of an ordinary Personal edit.Structure
The People tab shows the participant list and nothing else: no sections, no invitation to publish, and no lock on the tab. A Personal Parable opens in the fullest mode your participation allows, as every Parable does: Publishing for its Primary, so you can edit it at once. It shows the participation control at its top right, as every Parable does, with Peeking, Pinging and Publishing; a choice there changes how you work, not the Parable. Ponder hides the Release menu and the Push, Version, State, and Changes controls. In the Release menu’s place, the person with Primary sees Personal (see the last section). The people here still follow the group. The Refresh menu still selects Current data or a stored Report; reading data does not start publishing. Adding someone to the participant list switches the Parable to Published Versions in the same save, and that person can start their own set of Changes. It publishes nothing and sends no Ping, and nothing switches it back when people leave. The API’s Switch Collaboration mode between Personal and Publishing tool also switches it. Neither switch opens a set of Changes. Your first set starts at your first change, at Start Changes, or at an edit Ponder makes in a Problem.Storage
The web app has no control that returns a Parable to Personal, but the API’s Switch Collaboration mode between Personal and Publishing tool does. Only a person whose own Primary seat names them can make that change. When a Role or a Workspace holds Primary, move Primary to that person first. Back to Personal keeps the Parable’s content, its Releases, its Refreshes and their schedules. Copies in other Workspaces get none of the later edits, and the last Release sent to them can be older than the Newest Release. It removes every Publishing, Pinging and Peeking seat, and it Pockets every open Patch, colleagues’ Patches included. Nobody is told. Colleagues lose the Parable and cannot open, Restore or export their Pocketed Patches. To give that work back, seat them again, which switches the Parable to Published Versions. Then a person with Publishing or Primary Restores each Patch. Before Ponder asks you to approve Back to Personal, it lists each seat that the move removes, each Patch that it Pockets with the person who started it, and the last Release sent to copies in other Workspaces, or that no other Workspace has it.A Personal Parable that published before
Edits save at once and go into no Release, even when earlier Releases exist. The Release half of the reading control shows Personal to the person with Primary, in a Workspace and in Admin. Point at it, or press it, to read its hint. The hint says what Personal holds:- Never published: “Personal. Only you hold a seat, and each change saves at once.”
- Published before, with copies in other Workspaces: “Personal. Changes save at once and go into no Release. A Refresh runs the Newest Release, v1.4. Copies in other Workspaces do not get these changes. The last Release sent to them is v1.0.” That Release can be older than the Newest Release.
- Published before, with no copy, or after a Revoke took the Parable from every Workspace: “Personal. Changes save at once and go into no Release. A Refresh runs the Newest Release, v1.4.”