Peek to inform
Sources
Docs: Pinging
Web App: Choose the Inform form of a Ping when Ponder offers it for the current
Problem and target.
Peeking maps to informed attention. Use it when a person should know that
something happened but no response is requested. The recipient receives a
content-minimized notification owned by their inbox boundary.
- State what changed and why the person is being informed.
- Include only information safe for that recipient and Workspace.
- Do not attach hidden source identifiers or customer data.
- Do not phrase an Inform notification as a request that secretly expects work.
- Use a Consult Ping when a response or decision is actually needed.
Peeking does not grant access to the source Problem, Parable, Patch, Piece, or
Workspace. It does not create membership, permission, or responsibility, and
the sender cannot infer additional information from whether the target opened
their own inbox item.
The name describes the informed responsibility, not surveillance. Use the
ordinary Protection and collaboration controls whenever someone needs real
access to the underlying work.
Choose Peeking mode when reading
Peeking mode is available
for reading regardless of whether the person’s standing responsibility is
Primary, Publishing, Pinging, or Peeking. It hides authoring: Pieces cannot be
edited, no Refresh runs, and the tree lists Pages alone. The Problems and
Collaboration tabs still show when the person’s responsibility allows them, and
Collaboration is read-only. Peeking does not reduce the underlying access needed
to read the Parable.
A person without Ponder permission, such as a Viewer, sees a tree of Pages
alone in every mode. In a Lab, that person sees the app alone: no Files and no
Collaboration. Ponder or Lab package permission shows them.
