How Do I Connect Two Asite Workspaces?

You connect two Asite workspaces with a CDE integration that moves documents, drawings and attributes from one workspace into the other and returns responses on the way back. CDE Sync™ links both workspaces through dedicated accounts, maps attributes between them and logs every transfer.

Why two Asite workspaces need to share

Asite is widely used by owners, developers, contractors and public bodies, especially in the UK and on international programmes. It is common for a client and a contractor, or a programme and a project, to each run their own workspace. Each one has its own folder structure, attributes and workflows set up for that organisation's needs.

When documents need to move between them, the usual answer is manual. A document controller downloads from one workspace, renames to the other organisation's convention, fills in a different set of attributes and uploads again. Responses travel back the same way. Across a long programme, that work adds up and makes it harder to prove which version each party held.

What carries across between Asite workspaces

CDE Sync™ moves files with their version history and maps attributes between the two workspaces. Document number, revision, status and discipline arrive in the form the receiving workspace requires, even where field names or picklists differ. Responses and reviewed documents can return the other way. Every transfer is logged for audit.

The Asite integration page describes the connector in more detail.

How to connect two Asite workspaces, step by step

  • Agree between both organisations which document types move each way.

  • Compare the two attribute sets and agree a mapping for each field.

  • Request an Asite service account in each workspace from its administrator.

  • Connect both workspaces in the CDE Sync™ wizard and select folders on each side.

  • Map attributes and set the schedule.

  • Run a test transfer, review it with both document controllers, then switch on the full flow.

Programmes, projects and supply chains

Large programmes often run a programme-level workspace for governance and reporting, with separate workspaces for individual projects or contracts. Connecting them means approved documents flow up to the programme record automatically, while project teams keep working in the workspace set up for them. The programme sees a complete picture without anyone copying files.

Supply chains are another case. A contractor may run its own Asite workspace while delivering into a client's. Syncing the agreed folders keeps both aligned, and each organisation keeps control of its own permissions and workflows. Our article on supply chain CDE integration covers this pattern across platforms.

Running the connection is mostly about exceptions. Documents that fail a mandatory attribute in the receiving workspace are reported to a nominated person and fixed at source. Because CDE Sync™ is configured through a wizard, mappings can change when either organisation updates a picklist, without developer time.

Workflow alignment deserves attention too. Each workspace may have its own review and approval steps, and a document approved in one should usually start a defined step in the other. Mapping a status change in one workspace to a target folder or workflow in the other keeps both processes intact. That avoids a common problem where a document is approved by the client but sits unnoticed in the contractor's workspace because nobody told them.

Most teams start with a single document type, such as drawings, and extend to reports, models and correspondence once the rules have been proven.

Security and data residency

CDE Sync™ streams files directly between the two workspaces without storing them, encrypts data in transit and processes it in the Azure region you choose, which suits UK, European and Australian residency requirements. Each organisation controls its own service account. Utopia Digital holds SOC 2 Type II and Cyber Essentials. See the Security Trust Portal and the global data region map.

Asite to Asite and the Utopiaverse™

An Asite to Asite connection is part of the Utopiaverse™, the connected record Utopia Digital builds across your platforms. CDE Sync™ keeps both workspaces aligned, CDE Backup™ keeps an independent copy in your own Azure, CDE Migrate™ handles consolidation or moves off Asite, and CDE Archive™ captures the record at completion. AI Insights searches content across both workspaces, with cited answers. See also How Do I Connect Two Oracle Aconex Projects or Instances? and CDE Sync for Asite.

See two Asite workspaces connected in the monthly live demo, or talk to the team about your project.

Previous
Previous

Beyond File Sharing: Why Modern CDEs Need Smart Integration

Next
Next

How Do I Connect Procore and Asite?