Revizto ↔ Autodesk Construction Cloud
Sync keeps issues aligned between construction platforms, starting with Revizto ↔ ACC.
Sync is Overlink's issue-sync product. Admins connect the platforms with service credentials and publish chains. Contributors choose which issues flow through them. Nothing is ever deleted.
How it works
Three steps, one origin side
Each chain pairs a container on each side, such as a Revizto project and an ACC project. One side is the origin: it creates issues, and its twins appear on the target. Mapped fields stay in sync in whichever direction each mapping allows.
An admin connects and publishes
An admin connects each platform with service credentials the org controls, creates a chain between a Revizto project and an ACC project, picks the one origin side, maps fields and publishes.
Contributors prove visibility and choose issues
Contributors work inside a scope an admin delegated. They sign in to each platform only to prove what they can see, then elect origin issues to sync or link existing pairs. Their tokens are never stored.
Unmapped values land in the Needs mapping inbox
When the engine meets a value or field nobody has mapped yet, it shows up in the admin's Needs mapping inbox instead of failing silently.
Invariants we keep
Ten rules that never break
Each rule is enforced in code and checked by tests and reviews, not just stated here.
No deletes, ever
Sync never deletes an issue, comment or attachment on any platform. The connector contract has no delete operation.
Comments are add-only
We never edit or delete a comment. Edits and deletions made on a platform are not propagated.
Only the origin creates
Twins are created only on the target side and only from origin issues. An issue created on the target is never mirrored back.
Origin precedence on link
When you link two existing issues, the first sync makes the target match the origin on every mapped field. After that, per-field direction and conflict rules apply.
Service keys do the syncing
Only the service credentials your admins add read or write synced data. Contributor identities prove visibility and nothing else.
No contributor tokens are stored
A contributor's platform token is used during the request that proves what they can see, then discarded.
Fingerprints, not values, at rest
Snapshots, change detection and conflicts store keyed fingerprints of your values, never the values themselves.
Admins keep oversight
A contributor's lapsed identity or departure never stops syncing on its own. Admins revoke, reassign or pause.
Everything is attributable
Config changes, elections, links, approvals and views of decrypted payloads are all written to the audit log.
Unverified behaviour is flagged
Any platform API behaviour we have not tested against real responses is marked as assumed, with a note saying what is unverified.
Sign up to get started
Sign up with WorkOS, create or join your org, then connect service credentials for Revizto and ACC.