Versions & Publishing
As tools and workflows change, Rival keeps track of versions so you always know what’s live and can go back if something goes wrong. Publishing is how a new version becomes the one others use.
Versioning
Section titled “Versioning”Each meaningful change creates a version. That history means you can see what changed, when, and by whom — and roll back to a known-good version if a new one misbehaves. For anything running real business processes, that safety net matters.
Publishing, with the enterprise approval gate
Section titled “Publishing, with the enterprise approval gate”Publishing a new version follows the same governance as everything else:
- Admins can publish directly.
- Team members publish through admin approval — the new version is reviewed before it goes live for others.
This keeps the thing your team relies on from changing underneath them without a check.
Related
Section titled “Related”- The same gate for agents → Publishing an Agent
- Who can publish → Capability matrix