topic Re: Shared Sites in Cloud in Revit Cloud Worksharing Forum

Shared Sites in Cloud

orelWQB2X — Mon, 18 May 2026 06:14:23 GMT

Hello,

I’ve read a lot of information about Shared Coordinates and Shared Sites, but I’m still looking for the best practice workflow.

I have 3 models: one basement model and 2 building models.
The buildings are typical/repeated buildings and each one appears 6 times across the site.

I initially created the site model locally and published the shared coordinates/sites.

Now there has been a change to the True North angle and the project coordinates.

Is there a way to update these changes directly in the cloud models without repeating the entire shared coordinates workflow locally again?

What is the recommended workflow in this situation for ACC / BIM Collaborate projects?

Thanks.

Re: Shared Sites in Cloud

jose_Miquelao — Mon, 18 May 2026 13:40:27 GMT

1. Update the coordinates in the site model (cloud)

Open the site model from ACC (as a central model).
Adjust:
- True North (Manage > Position > Rotate True North)
- Project Base Point / Survey Point as needed:
  - Use “Specify Coordinates at Point” or manually set the coordinates at a known reference.
Save/sync the site model to the cloud.

At this point, the site model has the correct new coordinate system, but the building/basement models still “remember” the old published coordinates.

2. Re-publish coordinates from the site model into each building/basement model

The goal is to re-run the “Publish Coordinates” step, but this time entirely in the cloud environment.

For each building model and the basement model:

In Revit, open the site model (cloud central).
Link the building model from ACC:
- Insert > Link Revit > From Autodesk Docs / ACC.
- Use the same link type/origin as before (usually “By Shared Coordinates” or “By Origin”; the important point is to be consistent).
With the linked building visible and positioned correctly, use:
- Manage > Coordinates > Publish Coordinates
- Select the linked building model.
When prompted about the named site / shared site:
- Either update the existing shared site definition that you already used for that building, or
- If you use multiple shared sites per building (for the 6 positions), be careful to pick the correct existing site name for each link.
Sync the site model, then open/sync the linked building model so it can actually accept the updated shared coordinates.

Repeat for:

Basement model
Building A model
Building B model

All of this can be done with cloud-hosted models; you don’t need to “detach and work locally” unless you have performance or permission issues.

Special case: multiple instances of the same typical building

You mentioned each building appears 6 times across the site. There are two standard patterns:

Pattern 1 – Multiple Shared Sites for one building model

One building model (e.g. Building A.rvt) is used as a link.
In the site model, you place that same link 6 times.
For each linked instance, when you “Publish Coordinates,” you create/update a different Shared Site inside the building model (Site_1, Site_2, … Site_6).

In this pattern, when True North / coordinates change:

You still open site model, re-“Publish Coordinates” to each instance of Building A.
For each instance, choose the correct one of the 6 shared sites (so the building model’s internal “Site_1…Site_6” definitions get updated).
Then when someone opens the Building A model directly, they can choose which Shared Site (Site_1, Site_2, etc.) to activate to match the desired position on the site.

Pattern 2 – Single Shared Site + Instancing handled only in site model

The building model has only one shared site definition.
Instancing (repetition) is handled purely by how the site model positions the links.
The building model itself just knows “global coordinates” of one representative location.

In this pattern, updating coordinates is simpler:

You only need to publish the updated coordinates to that one shared site definition in the building model.
The six instances just fold that change in automatically, because they all reference the same shared coordinate system.

Best practice for ACC in complex sites:
Pattern 2 is generally more robust and less error-prone. Use multiple link instances in the site file, but keep a single shared coordinate definition inside the building model unless you truly need six internal sites.

Re: Shared Sites in Cloud

orelWQB2X — Tue, 19 May 2026 11:17:14 GMT

Thanks Jose, this is very helpful.
However, I think there are two important limitations in this workflow when working with ACC / BIM Collaborate cloud models and repeated building instances.

In cloud-based Revit models, the traditional Publish Coordinates workflow is not really supported/reliable the same way it was with local/Revit Server workflows.
Once all models are cloud models, coordinate management becomes much more limited, especially with multiple linked instances.

Regarding Pattern 2 (single shared site + multiple instances in the site model):
I understand the simplicity advantage, but I’m struggling with the consultant workflow side.

If the same building model is placed 6 times across the site, and a consultant needs to produce drawings/export IFC/NWC for a specific instance (for example Building A-5), how is that usually handled?

Since the building model itself only contains one shared coordinate definition, the different placements only exist inside the site model.
This seems problematic for:

discipline coordination
exports
instance-specific documentation
consultant deliverables
rotated instances

Because of this, I wonder whether in real ACC projects a hybrid approach is more common, where each repeated building eventually becomes its own cloud model instance (A1, A2, A3...) even if they originate from the same typical building template.

Re: Shared Sites in Cloud

ToanDN — Tue, 19 May 2026 16:58:24 GMT

Adjust the True North and survey point in the site model
Open each building model, Reset shared coordinates, select the site model link and Acquire Coordinates

Re: Shared Sites in Cloud

orelWQB2X — Wed, 20 May 2026 05:18:16 GMT

Yes, this solution can work when there is only one shared site definition per building model.

However, in my case I have 2 typical building models:

one building appears 4 times across the site
and the second building appears 2 times

That is where the workflow becomes more complicated in ACC cloud projects.

Re: Shared Sites in Cloud

ToanDN — Thu, 21 May 2026 00:56:11 GMT

@orelWQB2X wrote:
Yes, this solution can work when there is only one shared site definition per building model.
However, in my case I have 2 typical building models:
one building appears 4 times across the site
and the second building appears 2 times
That is where the workflow becomes more complicated in ACC cloud projects.

Save the ACC building model as a local model, link it in the site model, move it to location 1, record as location 1; move it to location 2, record as location 2; repeat. Save the model and follow the prompt to save the link with all locations recorded. Open the link and save as cloud mode to ACC.

Re: Shared Sites in Cloud

orelWQB2X — Tue, 26 May 2026 09:13:32 GMT

Yes I know that workflow.

But what is the workflow when the coordinate changes along the project?

Do I have to do all the proccess again locally?

Re: Shared Sites in Cloud

orelWQB2X — Mon, 08 Jun 2026 10:15:39 GMT

Re: Shared Sites in Cloud

FReinozo — Fri, 28 Aug 2026 06:01:27 GMT

Hi mate, did you find a solution to this issue? I’m having the same problem—one building model used across multiple sites. Publishing isn’t working for cloud-based projects, and I don’t want to download the building model and then re-upload it each time, as that would be a very tedious process. Hopefully Autodesk fixes this soon... Is there any pyrevit solution maybe?

Re: Shared Sites in Cloud

orelWQB2X — Sun, 30 Aug 2026 05:30:21 GMT

Unfortunately there is no magic solution other than working locally by moving/duplicating the instances.
There are some solutions like creating a position-only model for each instance when there are instances in the mirror.

If you found any other solution let me know.