​

Primary

Primary is the highest participation on a composed Parable. It includes Publishing, Pinging, and Peeking. Primary may name a person, a Role, or a Workspace. On an enrolled copy of a composed Platform Parable, it names Parable staff. Open People and choose Participants to see Primary, Publishing, Pinging, and Peeking on the selected Deployment.

​

Participation does not replace access

A protected action requires all applicable checks:

1. The person may enter the Workspace and use the relevant action.
2. Their participation on the composed Parable permits the action.
3. The composed Parable’s Policies permit the action. Primary does not bypass an empty Policy grant.

Provider Policies still govern Provider data. Primary does not grant Workspace membership or bypass Pros Access. The person who makes a composed Parable holds Primary on its source Deployment. A Workspace Administrator Role does not automatically grant Primary on every composed Parable in that Workspace. A person with Parable view access and participation can open the composed Parable from the Workspace directory. Reading does not require permission to build composed Parables or use Ponder.

​

Copies of composed Platform Parables

New copies of composed Platform Parables seat Parable staff at Primary and Publishing. Every Workspace member retains Pinging while Visible is on. A non-staff Workspace Administrator does not gain Primary or Publishing from that Role. The copy’s Policies decide which member actions are allowed. Policy changes arrive with Releases, not through a live read of the source Deployment’s Policies. Staff access to a customer Workspace requires a live Support grant for that person and Workspace. Impersonate and View as do not inherit staff participation. A hidden copy does not lend interactive Platform Primary or Publishing. Existing copies keep their previous participation until a separately approved migration enrolls them. A repeated Deploy does not enroll an existing copy. Do not infer staff-only authority from an older copy’s Primary. New non-Platform copies use ordinary participation until Platform turns on. For an enrolled copy, turning Platform on suspends its previous Primary and Publishing without removing named assignments. Turning Platform off restores unchanged assignments whose people or Roles still exist. It does not restore independently removed participation. Pinging and Peeking remain unchanged. A new copy retains its ordinary default participation for that reversal. An existing copy that deliberately had no Primary does not acquire one when Platform turns off. Revoke ends the deployed Platform participation on that copy. Existing named participation returns, while enrollment remains for a later Deploy. A later Deploy applies Platform participation again. Named assignment identities remain intact, and ordinary Pull and Release rules still apply.

​

Copies of other composed Parables

A new non-Platform composed Parable copy seats the Workspace Administrator Role at Primary if no Primary already exists. The Role follows the people who hold it in that Workspace. A later Deploy preserves a named Primary. Every member holds Pinging while Visible is on. Turning Visible off removes that Workspace participation. Existing named assignments retain their normal visibility rules.

​

Primary actions

Primary can change Primary participation on ordinary composed Parables. Publishing may change participation at its own level or below, but cannot replace Primary. The canonical Primary and Publishing on a managed Platform copy remain Parable staff when lower participation changes. Raising a paused Refresh’s budget requires Primary and the budget permission. Changing participation does not remove Refresh budgets or Provider restrictions. If an action is disabled, read its explanation. Check the selected Workspace, composed Parable, Patch state, participation, and required permissions.

​

Active participation mode

Primary is standing participation. A person with Primary can choose Publishing, Pinging, or Peeking for their current work. A narrower mode never grants additional authority. The mode changes what the page offers you. The page sends the mode with its own Pane and settings requests. The server decides those requests at the lower of your participation and the mode. The mode does not limit Ponder. Ponder and the MCP server act with your full participation, Primary included, whatever mode the page shows. So Peeking mode does not keep Ponder from a Publish, a Refresh or a seat change that you ask for.