OphioliteProduct / Sharing and review
Sharing and review
Share a version with the people who should read or reuse it, move it through one set of review stages, and refuse everyone else.
For teams that want colleagues to build on each other's work without losing control of it.
- Available Share work with the right people
- Partial Explicit result versions
Key features
- Read and reuse
- Reading a version and building on it are separate permissions.
- Conditional sharing
- A change to who may read names the version of the sharing it read, so no one overwrites another person's change.
- Policy-checked widening
- Widening an audience is checked against the project's rules.
- Review stages
- Request review, approve, return or withdraw one exact version.
- Result versions
- Append a version against its parent, group results and recommend one.
- Refusals
- People outside the audience are refused in the browser and in Python alike.
How it works
- Publish a result: it is private to you.
- Share it with a colleague to read, or to read and reuse.
- They build on it; their result names yours as its exact input.
Technical details
Every sharing change carries the expected generation it read; the server refuses a stale one rather than overwriting it. The same checks run for browser sessions, delegates and application sign-ins.
Not yet, and not planned
- Explicit result versions: Connector-owned inputs are not versioned this way
Not planned: suite-wide petrel or techlog replacement; a general application builder or marketplace; universal format conversion.