DriftSync
Get Pro

Team library & approvals

The team library is a shared, versioned home for your config bundles. Instead of passing files around, a team publishes bundles to one place, gates risky releases behind an approval, and gets a full audit trail of who changed what and when.

Pro

The team library, approvals, and shared audit are DriftSync Pro capabilities, hosted in DriftSync Cloud. They are opt-in and never gate the core loop — a single site can always export, diff, apply, and roll back on its own.

Versioned bundles

Every bundle published to the library keeps its version history. When someone updates a bundle, the previous versions remain — you can compare two versions, see exactly what changed between them, and apply or roll back to a specific version. Because a bundle is plain JSON, each version is a reviewable, diffable artifact.

  • One canonical location for the bundles your team promotes.
  • Full version history per bundle, with diffs between versions.
  • Apply a specific version to a site or a fan-out group.

Approval gates

An approval gate requires a reviewer to sign off before a release can be applied to protected targets — for example your production group. The person proposing a change and the person approving it can be different people, so a risky release always gets a second set of eyes.

  1. An author publishes or updates a bundle and requests approval to release it.
  2. A reviewer inspects the diff between the proposed version and what is live, then approves or rejects.
  3. Only an approved release can be applied to a gated target. Rejections send it back with a comment.

Note

Approvals gate which releases may be applied; they do not replace the per-site safeguards. The target still runs its own dry-run diff and takes a snapshot when it applies.

Roles

Team members hold roles that map to what they can do with the library — typically an owner who manages the team and gates, editors who publish and propose releases, and viewers with read-only access to bundles and history. Approval gates are configured per protected target, so you decide which destinations demand sign-off.

Shared audit

Every publish, approval, rejection, and apply is recorded in a shared audit trail. Combined with each site's own History panel, you get the complete picture: who proposed a change, who approved it, when it went out, and to which sites — and you can roll any of it back.

Related

Pair the library with multi-site fan-out to release an approved bundle to a whole group, and see DriftSync Cloud for where the library lives.