Limit assignment of issues in a project

Projects can consist of a lot of team members. When assigning an issue, this long list of possible assignees does not make choosing the correct person any easier. Some team members only need to be able to assign issues to team members within their own company or sub team.

In order to offer a clearer overview, and a shorter list of possibilities, there are two ways in which you can limit who a team member can assign issues to in a project:

1. Based on the team members' company
   
2. Based on the team members' user groups
   

Issue assignment limitations are only available in the Premium and Ultimate plans.

Limit assignment based on company

When a user is added to a private BIMcollab Nexus space, they are assigned to a company.

This property can be used to limit a team member to only assign issues to users who are part of the same company.

In order to do so, a Project leader can follow these steps:

1. Go to the Settings page of the project
   
2. Navigate to the Team members tab
   
3. Find the team member for who you want to limit issue assignment
   
4. Enable the slider 'Subteam (company)'
   

When the option 'Subteam (company)' is disabled, the user can assign issues to any other assignable team member in the project.

To make sure issues can be assigned across companies, have at least one user in every company who is able to assign issues to everyone. The image below illustrates that within each company one user can assign issues to users from other companies.

Limit assignment based on user groups

In the Project's settings, you can enable the option 'Only allow to assign issues to members of the team member's usergroup(s)'.
When this option is enabled, team members can only assign issues to other team members who are part of the same groups. This workflow is more flexible than the one based on companies, because a team member can be part of multiple groups.

As an example, everyone in a (sub)team within a project can be part of a separate user group in BIMcollab. These groups are illustrated as Subteam 1-3 in the image below. Within every user group, one person should be responsible for communication with the other groups. These responsible persons are the Team leaders in the image below. These team leaders can be dded together to an additional user group, so they can assign issues across the user groups.

The limitation based on company and based on user groups can be used together, when multiple companies are part of the same user group or a company is divided into subteams. These workflows do not exclude each other.

For more information on the issue visibility in combination with user groups, consult the article User groups and issue visibility.

To know how to create user groups, consult the article Define project properties.

• Related Articles

• Define project properties

  After you have created a new project you can now change the project’s properties so that it meets your requirements. Do you want to advance your knowledge about BIMcollab Nexus? Go toour BIMcollab Academy and enroll in the BIMcollab Nexus course. Go ...

• Monitoring BIM projects in graphs

  Keep track of BIM project progress and workload BIMcollab Nexus provides you with an overview of all issues in a project and the projects' progress, using a series of summary graphs. To see these graphs, click 'Show graphs' on the Issues page of your ...

• Good issue management

  Using an issue management platform like BIMcollab Nexus can save time, avoid mistakes and create transparency within a team. As powerful as BIMcollab’s issue management may be, if it is not used in a structured way, the full potential may not be ...

• Limit team members from closing issues

  In the project settings, a project leader can choose which of the team members can close issues. On the Project settings page, you can find the option 'Issue can be closed by' in the 'Workflow' section. The options are: Everybody (project leaders and ...

• 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 ...