The fact that I’m posting about it means that it probably isn’t really that easy, right? There are a few challenging pieces of the puzzle that all need to come together to get C4R or Collaboration for Revit working on a real project. I just went through this process with a mechanical firm so it is all pretty fresh in my mind.

Firstly, note that A360 Team has been rebranded as BIM 360 Team and will be migrated, more details at this post.

Secondly, Autodesk really wants your whole team (like everyone, every consultant, every Revit link) on Collaboration for Revit. However, out in the real world it is just happening bit-by-bit, and in the meantime some hacks and workarounds can make the process a little bit easier.

A Quick Overview
Ok, so Collaboration for Revit runs on top of BIM 360 Team. What this means is that you need to have an active BIM 360 Team license if you wish to run projects. Then, you need a Collaboration for Revit license for each Revit user who will be connecting to that BIM 360 Team site. You still with me? This also means that persons outside of your firm may connect to your projects, provided they have their own Collaboration for Revit entitlement applied to their Autodesk account.

Once you have the BIM 360 Team license, and the Collaboration for Revit licenses, you then need to “Assign” the Collaboration for Revit licenses out to the users (using their Autodesk login details).

Finally, you need to actually do some stuff, like:

  • make a BIM 360 Team project,
  • invite the users,
  • initiate Revit models, and
  • get the links working.

Its a lot to take in, so you can see that the blog title is actually a half-joke 🙂 However, we were able to get all this up and running in about 4 hours for one firm, so you can too. Hopefully.

Something that will help
Given that there are a lot of moving pieces, I turned to my favourite research and documentation tool, OneNote. I have created a public notebook that you can view at this link:
Revit Collaboration Public Help


Basically all of the steps involved in getting the licensing setup, inviting users, installing the addin, and initiating models onto Collaboration for Revit are in the notebook linked above. I will continue to update and add to this over time.

Any Questions?
Just comment to this post and I will endeavour to answer your question in the notebook, or point you toward the answer.

Now, here are a few other bits and pieces that may be useful, if the notebook doesn’t answer your questions…

new help documentation:

moving models to folders:

You can move projects from A360 Free to a paid BIM360 Team hub by using the Transfer function:


Taking models offline and replacing later:

using local linked files

Download links:
Collaboration for Revit 2017
Collaboration for Revit 2016

Collaboration for Revit 2015

Recent chat with Autodesk

I have posted many times over the past few years about Project Skyscraper, which then became Collaboration for Revit (C4R). Having used the cloud service in beta, I was keen to get it going on some live projects. Unfortunately, Collaboration for Revit was only available in the USA…

Until now, that is! Check out this press release for details on the global launch. Quote:
Released and available in North America only since December 7, 2014, Collaboration for Revit will be available for commercial global use as of January 7, 2016.  




Autodesk A360 Collaboration for Revit is a service that works with Revit software to connect project teams with centralized access to BIM project data in the cloud.  Image courtesy of Autodesk

I, for one, am very excited about this. I have been involved in at least one geographically distributed vanilla Revit Server setup, and I think that the necessity to have ‘my IT people talk to your IT people to set up a DMZ between our VPNs’ is a bit counter-productive. In these situations, the global availability of C4R will really shine. Now, firms will be able to spin up a C4R instance very quickly and get working together, on real projects and in real-time.

You can hear Ralph Bond interviewing Sylvia Knauer on the Autodesk AEC Channel Podcast here in this mp3.

Between this global launch of Collaboration for Revit, and the improvements in the Glue – Navisworks connection in 2016 products, my Federated Model Streamer concept is one step closer to reality 🙂