Skip to main content

Participants

Participants are the people, Roles, and Workspaces that hold a participation on a Parable. The four participations are Primary, Publishing, Pinging, and Peeking. They exist so everyone can see who may do what, and so Parable actions and Policies can be granted to the right participations instead of to whoever happens to be asking. Each assignment holds one of the four participations, and each higher one includes everything below it. Primary may do everything that Publishing may do. Only Primary may also give, move, or remove Primary, switch between Personal and Published Versions, raise the budget of a Pipeline that paused at its caps, and Prepare and Patch a Pull that another person started. By default, only Primary changes the Policies of a Page or a Pane. Publishing may edit Pieces, Propose, Prepare, and Publish a set of Changes. It may also Pull a Delivery, run a Refresh, run a Preview, and give Publishing, Pinging, or Peeking to other people. Pinging reads and works in Problems without editing Pieces. Peeking reads Pages, chooses a Version, Changes, or Report reading, and can send Messages to Ponder in a Problem it can see. A Ponder turn runs with the sender’s permissions, so a turn for a person who holds only Peeking saves no Changes. A participation on a Parable does not decide who sends or answers a Ping. Pinging on the Pings Platform Parable decides it. Primary can be a person, a Role, or a whole Workspace; when a group holds it, everyone in that group holds it together. A Parable can have several Primaries at once, so one person is never the only one who can act on it. Participants are managed in People under Participants, which has a picker for people, Roles, and Workspaces and one row per assignment. The picker lists the people of the Workspace that the Parable belongs to, in the app and in Admin, so a Parable Pro who may read that Workspace finds its people. A Parable Pro also finds every Parable Pro who can hold a seat there, whether or not they are a member of the Workspace, and each one is marked Parable staff. Only a Parable Pro finds Parable Pros through the picker’s search, and only a Parable Pro sees that mark. A customer still sees the name of a Parable Pro who holds a seat. When a list cannot load, the picker names it, for example “People could not be loaded.” A Parable Pro’s list of Parable Pros is the one exception: when it cannot load, the picker still shows the Workspace’s people and Roles. Participants apply when the Parable is in Publishing mode. A Personal Parable seats only the person who holds Primary. A participation and access are separate. An assignment on its own gives nobody Workspace membership or access to a protected Parable, and a Workspace administrator does not automatically hold Primary. A protected action runs only when the person can use the Workspace surface, their participation permits the action, and current Policies allow it; Primary does not bypass a denied Policy. A person row names an active member of the Workspace that the Parable belongs to, a person with an open invite to it, or a Parable Pro, member or not. Here a Parable Pro is a Parable employee with a live account and a live staff Role that can read Parables. A Parable Pro’s row lets them do nothing until they can enter the Workspace, for example through Pros Access. A suspended member, a deleted account, and a person whose invite expired or was revoked are not members. A save that adds anyone else, moves such a person to another participation, or names nobody is refused. The sentence names each person who is or was in the Workspace or holds a seat on the Parable, and counts everyone else as from outside this Workspace, for example “Only members of this Workspace can hold a seat on its Parables. Lena Left and a person from outside this Workspace are not members. Invite them to the Workspace first.” A row that the list keeps as it is stays, so a person who left the Workspace does not block a save. A kept person row whose id names no account, deleted or not, is removed from the saved list, and the save continues. The one exception is the Primary row of an origin, which stays. Nobody holds that row, so no save can give Primary to someone else. Parable staff repair it in the data. When the person who saves may not make the change, the save is refused for that first, before any member check. A Parable always keeps at least one Primary. Publishing can give Publishing, Pinging, or Peeking to others but cannot change Primary or take it. Only a Primary gives Primary: to add a second Primary, keep your own row and add theirs. A Primary who leaves their own row out of a list that names another Primary keeps Publishing. To leave the Parable, they remove their own row in a later save. That save answers with the saved list. After it, they no longer see the Parable unless another row gives them a participation. On a Personal Parable the hand-over therefore seats two people, so the same save switches it to Published Versions. Renaming a Role does not change its participations. Returning a Parable to Personal removes the other participants. The person who returns it must first be its only Primary, so every other Primary row goes first, a Role or Workspace that holds Primary included. A mention, Ping, Power, or Ponder Message never gives a participation. Participations are different from the View mode (the Active Participation Mode) that a person picks for the moment: Publishing, Pinging, or Peeking. The mode changes what the page offers the person. It does not limit Ponder. Ponder and the MCP server act with the person’s full participation, whatever mode the page shows. The page sends its mode with its own Pane and settings requests. The server decides those requests at the lower of the person’s participation and the mode. A person who holds Primary or Publishing can pick any mode. A person who holds Pinging can pick Pinging or Peeking. A person who holds Peeking can pick Peeking. The Participants picker offers only the participations you may give. A person who holds Primary sees all four. A person who holds Publishing sees Publishing, Pinging, and Peeking. The row of a person or group that holds Primary shows Primary as held, and every control on that row is off. In a Workspace, if you may see the Roles of Workspace members, a row at Primary or Publishing whose person lacks Build Parables there says so: “Publishing, but they lack Build Parables in this Workspace, so they cannot change the Parable.” Such a person still reads the Parable, and can still save their own values where the Policies allow. With the same access, a Role row whose Role lacks Build Parables says there that only its members who have Build Parables through another Role can change the Parable. If you may not see the Roles of Workspace members, the picker shows no such note.
  1. Ask Ponder who holds a participation on the Parable. It reads the current assignments before proposing any change.
  2. Describe the change in plain words, such as making a Role the Pinging participants, adding a second Primary, or moving Primary to a named person. Name the person, Role, or Workspace exactly; Ponder looks people up in the Workspace and asks when a name is ambiguous.
  3. Ponder replaces the whole assignment list in one step, so it keeps every unchanged row, keeps at least one Primary, and presents the new list for your approval.
  4. Approve only if the list matches your intent. The save fails if someone else changed the assignments first; read them again and retry.
  5. If someone needs access rather than a participation, handle Workspace membership separately.
Good assignments name a Primary and a second Primary who can act when the first is away, a Publishing participant who does the work, and only the Pinging and Peeking participants who need them. Check the result by reading the assignments back and by confirming that each person sees the modes and actions their participation allows. A disabled action explains which participation it needs; read that explanation before changing anyone’s participation. Related Powers: Publishing, Policies, Pings, Workspaces. Find each by its title; do not guess stored names.