Bridge Box — where the office, contracts and clients live — and Dalux — where the site teams work on the iPad. DMS Sync Manager moves drawings, models and metadata between the two on a schedule, so nobody has to download from Box and upload to Dalux by hand.
Three steps to keep Box and Dalux in sync.
Box authenticates with OAuth 2.0 against your Box enterprise. Dalux uses an API key issued by your Dalux tenant administrator. Each project keeps its own pair of connections, stored encrypted at rest.
Pick a Box folder as the source (or destination) and a Dalux project + document area on the other side. Box metadata templates map to Dalux metadata fields, with direction set per sync task.
Rules filter by file type (PDF, DWG, IFC, RVT), label, revision, or last-modified window. Schedule hourly, every 6 hours, daily, or on demand. Every run is logged file by file.
A few real-world scenarios.
"Projects rarely fail in design — they fail when teams can't trust they're looking at the latest version."
This pair targets Dalux Box / Document — the document storage layer — not to be confused with Box.com. Dalux Field issues, snags and inspections are out of scope; they stay in Dalux Field.
Yes. IFC 2x3, IFC 4 and IFC 4x3 pass through unchanged — bytes-identical at the destination. Models keep their property sets, geometry and structure.
Yes. Each sync task lets you map Box metadata template fields to Dalux metadata fields of your choice, so revisions carry their identifiers across.
Each new revision arrives as a new version in the destination, preserving Box's native version history. The revision label is written into the configured Dalux field.
Sync workers run in eu-west-1 (Ireland). Files transit through the workers but are not retained; only metadata and audit logs are stored. For Box itself, EU data residency is available via Box Zones.
Book a demo and we'll walk you through setting it up for your project.