Project information includes the key details about your project, including:

(a) Assign the project to a department within a division, to categorize a project to a specific sector.

(b) Mark a project as active or inactive, to control it's visibility and editability.

(c) Toggle the Allow administrators to access the project to allow or restrict administrators' access to the project.

As well as additional project workflow options that apply directly to Issue management:

(d) Set the Project owner, who is the default user to whom issues will be assigned if no other user is chosen at issue creation.

(e) Define the Mandatory fields that are required during issue creation and editing.

When configured, users cannot create or update an issue without completing these fields.

(f) Specify who can close issues, everyone on the project or restricted to specific groups.

(g) Restrict issues' assignment so that users can only assign issues to team members within their own group(s), which prevents cross-group assignment.

(h) Use the approval workflow so that issues require formal approval before reaching a final status.

(i) Manage visibility settings: when this field is activated for a project, it is possible to define which team members can view the issue when an issue is created.

(j) Activate the use of custom list fields, which can later be refined in the Custom Fields settings, to enable project-specific properties.

The Team members menu allows project leaders to manage team members and review key information about all invited users in the project.

Project leaders can (a) add new members, or manage team members by clicking on the three dots menu to:

(b) edit team member information and rights or,

(c) remove existing members from the project,

(d) as well as filter the user list per Active and Removed status to efficently manage team meebers.
​

The table displays each member’s essential information, and permissions such as:

(e) Group: Lists the user groups to which the member belongs. Groups can be used to manage issue visibility.

(f) Assignable: Indicates whether the member can be assigned to issues. When enabled, the member appears in the assign list in the issue menu.

(g) Can import: Specifies if a member can import BCF files.

(h) Zoom editor: Indicates whether the member has permission to create and modify Zoom checking rules in the Shared folder.

(i) Issues: Displays the total number of issues currently assigned to them.
​

Certain BIMcollab CDE tiers offer the option to use project phases within the project lifecycle for Document Management. This menu provides direct access to the CDE project settings page, where phase details can be configured and managed.
​

The Integrations tab enables connections with external platforms, allowing models stored in connected applications to be viewed directly in the BIMcollab WebViewer. Users can browse linked folders, select available models, and load them without downloading or manually uploading files.
​

The available integrations are:

From this menu, each team member can set their email notification frequency preferences. Also, the Project leader role will have the option to select how often they would like to receive a report of all activities.

Milestones are created to identify specific goals or stages in a project. When creating a milestone, give it a clear name, and define a start and end date. These dates will be used to highlight issues that are beyond their due date.

When editing a Milestone, you can activate or deactivate it by clicking on the button Assignable. Only milestones which are assignable are available as a value when creating or editing an issue.

Areas allow team members to group issues by building sections, stories, or subprojects.

Labels can be very helpful when filtering issues. They are fully customizable and can be used to define the discipline, the model, or any other custom metric for your project.

Type is used to distinguish between different types of issues. For example, clash detection, request, question and similar.

The default type column indicates which type is automatically selected when creating a new issue in the project. Project leaders can change the default type by clicking on the three dots menu and selecting Set default.

Priority indicates the urgency of an issue. By default, there are five priority levels available.

While the (a) order of the levels is fixed and cannot be changed, the (b) priority names can be modified by clicking the three-dots menu next to the priority and selecting Edit.

The default priority for newly created issues is always set to number 3.

Groups represent the sub-teams within your project.

They can be used to:

Once defined, users can be assigned to one or more groups.

To assign a user to a group:

From the Team Member menu, click on the name of the team member, and in the Edit team member menu, assign them to group(s) as needed.
​

​

Custom fields allow you to define project-specific properties which can be used to add additional information to the issues in a project.

You can add (a)-(b) two list fields and (c)-(d) two text fields.

Within the BIMcollab, information can be linked to your files to facilitate filtering, searching, and overall usability. This information is known as metadata fields.

Metadata fields are created by administrators in the CDE administration side and can be specified at both the project and phase level.

Common metadata fields may include:

Workflows represent a standardized series of actions (such as audit, review, stamping, or notifications) designed to automate common document procedures. In the Workflow menu, members can check whether a workflow is (a)active, as well as review its (b)name, (c)order, (d)description, and (e)associated spatial structure.

All workflows are created in advance by administrators in the CDE administration side.

Work package codes are used to manage deliverables or work packages efficiently within a project.
From the Work package code page, members with the right permissions can (a)add new work package codes to the project. Each work package code is identified by: (b)name, (c)description, (d)owner, and (e)work packages associated.
​

Document naming conventions is a standardized structure for document names to ensure consistency, clarity, and traceability across a project.
It can be linked to a project or specific phase by Project Leaders or users with the appropriate permissions, using the (a)Edit button. Once applied, all team members can view the active naming convention from this page.
​

Document upload settings define the upload method chosen for the project. There are two upload options:

Project leaders and users with the appropriate permissions can adjust this behavior using the (a)Use advanced document upload toggle. Once activated, a (b) list of all current mandatory metadata fields will be displayed below.