twitter youtube facebook linkedin email
Connect with:

BIM 360 Release Notes

BIM 360 Docs Update – November 7, 2018

Joan Allen
November 7, 2018

Introducing BIM 360 Review and Approval Workflow

We are pleased to announce the immediate availability of the new ‘Reviews” feature in BIM 360 Document Management.  This feature provides the following capabilities to document managers and project team members:

  • Enables Document Managers to facilitate, control, and automate the review and distribution of project drawings, models, and other documents and
  • Provides project team members with an easy, intuitive experience for reviewing, commenting, and approving project documents.

What is included in the new Reviews feature?

  • Workflow Templates – Project Admin can select, name, and configure participants, status labels, and durations
  • Initiate Workflow – end user can select documents and start a review/approval workflow (based on configuration by Project Admin)
  • Notification – assignment and email notifications
  • Markups – Create, manage, and track document level markups
  • Comments – Create, manage, and track document level comments
  • Approval – document level status with configurable terminology
  • Action after approval – display status in document list, copy to another folder (e.g., WIP to Shared; Shared to Published…)
  • Available US and EMEA Data Centers

Configure Review and Approval Workflows

To get started, you will need to create one or more workflows in Project Administration > Document Management > Reviews

Choose from several workflow templates (1, 2, or 3 steps)

Then, configure the workflow – name, participants (users / roles / companies), durations, status labels, and action after approval

Participating in a Review and Approval Workflow

Once you have configured one or more workflows, your project team can get started.  Team members with “initiate” permissions will be able to select one or more documents and choose the “Submit for review” option in the menu:

Depending upon the workflow configuration rules, the project members may be able to choose between one or more workflows.

An email notification will be sent to the next participants in the workflow.  You can also choose to notify other project team members.

The assigned team members will then go through the review process, with the ability to add markups from within the viewer and add comments for each document.

In the final step, the Approver will set the approval status on a document-by-document basis (note that this is version-specific).  In all cases, the documents will remain in the original folder, with the the approval status displayed.  Depending upon the configuration set up by the Project Admin, an additional action, in which the approved documents are copied to another folder, may occur.  This option is designed to support making approved documents available to a broader group, such as “Work in Progress (WIP) to Shared” or “Shared to Published” workflows.

To learn more, please review to our online help documentation.

We intend to add more workflow capabilities in future releases, and we look forward to hearing your feedback!

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

Joan Allen

Joan leads product management for BIM 360 Docs. Joan is a registered Civil Engineer with over 25 years of experience in construction management and technology for the AEC industry. Since joining Autodesk, she has focused on delivering innovative, cloud-based solutions for connecting AEC project teams and improving project delivery workflows, including Autodesk BIM 360 Glue and Autodesk Buzzsaw.


View by:
Most Recent Oldest

    I had a query on Approval Workflow.
    If suppose, there is only one step approval flow Initiator—->Approver
    Initiator being the architect and Approver being document manager.
    In that project- there is one imitator and multiple users mapped to document manager who are the approvers

    After the document is submitted for review by initiator , the notification flows to document managers, now suppose one approves, how will the other users approve the document and how will the status be like? Can you please help us understand the same.


    action upon completion error, please help!

    1. AvatarMike Davison

      Hi William:

      If you are getting an error, please contact your Autodesk support representative to report the problem.



  3. Avataralejandro.iturriaga.aecom

    I wasn’t able to add add markups in a review process. I was using Mozilla Firefox. I would be able to create the markups but when I tried saving the would save for a few seconds and then disappear. Any suggestions?

    1. AvatarJoan Allen (Post author)

      Hi Alejandro,

      Today the markups in the review process are “published” markups, so that everyone in the process can view those markups. The permission to create published markups is the same in the review process as it is from the folder experience – this requires “edit” permission. It is likely that you had a permission lower than “edit” on the folder. We are working to improve this experience.

      Best Regards,
      Joan Allen
      Autodesk BIM 360