Org sync and staged rollout
How policy and flow changes reach every desk, and how to test a change on one team first.
Every policy or flow change creates a new revision. Revisions sync to every connected desk automatically, usually within minutes, and instantly with `verybear sync` run on a specific desk.
terminal
Copy$ verybear sync
✓ pulled policy revision r185
✓ 11 flows active, 0 draftStaged rollout
On Business and Enterprise plans, a flow or policy change can target a single team first. Publish to Engineering, watch quality and spend for a day or a week, then promote to the rest of the org, or roll back before anyone else is affected.
- Stage a change to one team from the flow editor's "Rollout" tab.
- Compare quality and spend for the staged team against its prior version.
- Promote to everyone, or revert. Both are one click, and both create a new revision.
Auto-sync can be turned off for a specific desk during debugging, but it's on by default org-wide.