The approval workflow

The approval workflow

The approval workflow  is a more formal way of working that allows for the resolution of an issue to be first checked and approved before being marked definitively as closed. This way you have more control over the resolution of an issue. With the assistance of an extra issue status and colors , the management of issues can be done in a more transparent way, guaranteeing that no issue is ever closed without proper reviewing.
The approval workflow is only available for Connected and Enterprise BIMcollab Cloud plans.

Enable the approval workflow in a project

The approval workflow can be switched on or of for every seperate project in your space. To enable the possibility to approvers to issues in a project, follow the steps below.
  1. As a Project Leader, go to the settings of the project.
  2. Switch on the toggle 'Use approval workflow'.
     

  3. Once the toggle is on, the field 'Approval' will appear in the issue settings.

The lifetime of an issue in the approval workflow

The status of an issue will change throughout its life cycle. There are three default options available for the status of an issue:  ActiveResolved, and  Closed. When the approval workflow is enabled, another status is added to the available options:  To approve.
  1. When creating an issue, assign the issue to the person who needs to resolve the problem, and select users who need to approve the resolution of the issue after it has been resolved.
    After creation, the status of the issue will be Active.



  2. The person to whom the issue is assigned, will implement a solution for the problem, and mark the issue as Resolved. The resolution will need to be approved by the team members who have been added to the Approval field. They will get a notification that they have to approve the issue, and the issue will be marked in purple.
  3. The approvers can reject the solution of the issue so the status becomes Active again, or approve the solution, so the status changes to Resolved, Approved. The issue will be marked in blue for all users.



    Learn more about the color of issues.

  4. Once the issues are approved, they can be Closed.



Who can approve issues?

Any user with the role Project Leader, Editor or Reviewer can be selected as an approver.  Approvers can be added either when the issue is created, or afterwards by editing the issue.  It is also possible to batch edit issues and choose common approver(s) for multiple issues at the same time.

Please note that in this workflow, once an issue is resolved, it will automatically be marked as  To approve for the approver(s). However, that does not prevent other users from closing the issue before the approval. To prevent that, good commun ication is necessary: if an issue is marked in purple, it should be agreed that it should not be closed by team members before being marked as  Approved . It is also possible to  limit team members from closing issues.

    • Related Articles

    • Enable workflow features for projects in a Connected or Enterprise space

      When a project leader creates a new project in a Connected or Enterprise space, they have some additional options that are not available in the free or Starter plans: Only allow to assign issues to members of the team member's usergroup(s) When this ...
    • Colors of issues based on their status

      The title of issues in  BIMcollab Cloud, BCF Managers, and BIMcollab ZOOM will be in different color based on their progress status. Read more about approval workflow and progress status in Classifying and Structuring Issues. The issues can have the ...
    • Classifying and structuring issues

      To be able to organize and structure the issues, it is necessary to define as many properties as possible. The more detail an issue contains, the better to situate it and work with it.  Start by defining the issue's Type, Area, Milestone, Labels, ...
    • Why can an issue be closed that I haven't approved?

      The approval process does not overrule other’s ability to close an issue. Therefore it is possible to close an issue which has not received all of it’s approvals. To see who closed the issue, check the issue’s history.
    • Limit team members from editing issues

      A team member with the role of viewer can only view issues within the project, but can't edit anything.  You can also give team members the role of reviewer. In this case they will be able to leave comments and approve issues when they are added to ...