twitter youtube facebook linkedin email
Connect with:

BIM 360 Release Notes

It’s been a while since we’ve updated you all on the state of the art for Admin in BIM 360. We’re happy to break the silence today, and announce a major improvement to the way we handle newly invited (pending) users across the BIM 360 ecosystem.

Until today, when you invited someone to a project or account in BIM 360, you would have to wait until they log in to start interacting with them. No assigning issues, no RFIs, no sharing files, and so on until the person logs in for the first time. For all intents and purposes, pending users were inaccessible until they logged in.

As of today, pending users are (in most cases) treated the same way everyone else is in BIM 360.

There’s a lot of detail hidden in that short sentence, so let’s break it down and clarify what exactly this means in context. You can now:

Document Management

  • Assign file and folder permissions to pending users
  • Assign transmittals to pending users
  • Share files with pending users
  • Add pending users to approval workflows

Cost Management

  • Award contracts to pending users and companies associated with them
  • Send documents to pending users

Project Management

  • Assign RFIs and submittals to pending users
  • Assign pending users to roles in RFI and submittal workflows
  • Add pending users as invitees or assignees for a meeting


  • Add pending users as owners or assignees for issues
  • Assign issue permissions to pending users
  • Add pending users as watchers for issues
  • @mention pending users in comments
  • See pending users in reports
  • Filter issues by assignee when the assignee is a pending user


We are working through enabling all existing pending users to take advantage of this new feature, so some folks you invited 6+ months ago may not work just yet. Stay tuned as we work through that, and continue to improve the admin experience in BIM 360!

MktoForms2.loadForm(“//”, “572-JSV-775”, 2332);

#mktoForm_2332 > div:nth-child(3) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoGutter.mktoHasWidth{
#mktoForm_2332 > div.mktoButtonRow > span > button{
color: #fff;
background-color: #1858A8 !important;
background-image: none !important;
border: 0px !important;
#mktoForm_2332 > div:nth-child(3) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoLogicalField.mktoCheckboxList.mktoHasWidth.mktoRequired, #mktoForm_2332, #mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField
{width: 100%!important;}
#mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol > div.mktoOffset,#mktoForm_2332 > div:nth-child(3) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoGutter.mktoHasWidth, #mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol > div.mktoFieldWrap.mktoRequiredField > div.mktoGutter.mktoHasWidth{
display: none;
width: 75%!important;
width: 84px!important;
#mktoForm_2332 > div:nth-child(2) > div.mktoFieldDescriptor.mktoFormCol{
margin-top: 10px;
width: 100%;

Subscribe to email digests.

Featured Links

Matthew Wellstein

Matthew is a Product Manager with Autodesk Construction Solutions.


View by:
Most Recent Oldest
  1. Avatarmac_EH

    This is good to have, but what we really need is more flexible permission options. Currently you need to give members full Download + Upload + Edit access to a folder so they can create markups, which is a security risk. it should be tickbox for different permission options instead of progressive levels.

    1. Avatarmac_EH

      * so they can ‘publish’ markups

  2. Avatarondrej.marsik

    Ok, I am trying to be positive but you guys dont give me much of a choice. This is update after two months of waiting ?! Pending permissions ? Except of what mac_EH wrote bellow…We need to copy and export issues and checklists templates from one project to another (after the project is created and not only by copying setting when newly created), email notification settings for users (this one should be really top priority), location linked to specific file (like in old field). I think most of us were or still are using OLD GEN and we created our workflows according to functions of the program. After so many months…NEXT GEN is still focusing on some new features without implementing basic functions from OLD GEN and this is keeping us from using it on real projects. It is really frustrating to explain our emloyees that: This is the NEX GEN…better one. And than I have to say: But you cannot longer use this, this, this and this doesnt work at all.

  3. Avatarmac_EH

    Agreed. 360 is very much moving in the right direction, we all believe in the grand vision and are working hard to promote it to our management and teams, but it needs faster development as there are still many unresolved basic fundamental ‘bim360 issues’ which are still holding many companies back from migrating. If you are increasing the price, you need to significantly increase thorough testing on real project scenarios, especially for bim360 docs and have monthly bulk updates to get it where we all need it to be.