Add a workspace-level organizational capability in Autodesk Forma similar to the workspace experience available in PlanGrid.   It's important to have the ability to create a secondary workspace under the primary workspace so our GIS group can highlight, markup and add notes without affecting the inspector's primary workspace. The secondary workspace is important because it filters down revision updates from the primary to the secondary seamlessly. Please replicate this option from PlanGrid into Forma Build.  Please use this reference from PlanGrid Workspaces: https://help.plangrid.com/hc/en-us/articles/115015369668-WorkspacesWorkspaces – PlanGrid Show More

Add a workspace-level organizational capability in Autodesk Forma similar to the workspace experience available in PlanGrid.     Can you please replicate the PlanGrid Workspaces option in Autodesk Forma Build? It's important to have the ability to create a secondary workspace under the primary workspace so our GIS group can highlight, markup and add notes without affecting the inspector's primary workspace. The secondary workspace is important because it filters down revision updates from the primary to the secondary seamlessly. Please replicate this option from PlanGrid into Forma Build.    Please use this reference from PlanGrid Workspaces: https://help.plangrid.com/hc/en-us/articles/115015369668-WorkspacesWorkspaces – PlanGrid    And I've copied and pasted of the web page in case it ever disappears:  Workspaces Note: The Workspaces feature is enabled on an organizational level. To have the workspaces feature enabled for your organization, please click the blue "?" in the lower left and type "contact support" so we can have a representative reach out. Featured: What is a Workspace? Creating a new Workspace Viewing a Workspace Adding sheets to a Workspace Markups and Workspaces Workspaces and Documents Workspaces and Team members Versioning and Workspaces     What is a Workspace? What is a Workspace?   With Workspaces you can create sub projects to break up specific parts of the project to focus on project areas or crews. This offers significant flexibility in how your team collaborates, while still connected to the main project. When Workspaces is activated for an organization, every individual in that organization will have the ability to create a workspace on any project that they participate in. Field reports, RFIs can be used in a workspace in the same way they are used on a project. The field reports in a workspace are only visible inside a workspace, and any forms can be used - just like in a project. Creating a new Workspace   Creating a new Workspace When you enter the projects list page in plangrid.com, click on: "New! Create a workspace" below the projects you would like to create it for   jhiggins_0-1787171794417.jpeg     Type a name for your workspace, and click on "Next" jhiggins_1-1787171794511.jpeg     You will then be able to select the team members that you would like to have access to the Workspace. Only people currently in the project can be invited to a workspace. If there is someone that isn't on the project that you would like to invite to a workspace, a Project Administrator will need to add them to the project team. The list of people in a project are shown grouped by Company Name folder, if they have filled out their company information. If there is no company information available, then the folders will group people by domain. Select one or several people at one time. Every selected team member will be added automatically to the workspace as a collaborator. The creator of the workspace is added to the workspace as an administrator by default. Click on "Next" once you are done selecting the team members.   jhiggins_2-1787171794656.jpeg     You can then select the sheets you want to share or work on with the selected group. The sheets are grouped by tags if tags have been set up on the project. Otherwise sheets are grouped by first letter initials. Click on "Next" after you are done selecting your sheets Note: Sheets can be added or removed from a workspace after the workspace has been created, so there is no need to worry about missing one or two in the Workspace creation process.   jhiggins_3-1787171794549.jpeg     The last step of the process is to select the documents you want to share or work on with the selected group. The documents are grouped by folders set up on the project. If there are documents that aren’t saved to a folder, they will appear in the “Other” folder. Click on "Finish" once you are done selecting your documents. Note: Documents can be added or removed from a workspace after the workspace has been created, so there is no need to worry about missing one or two in the Workspace creation process.   jhiggins_4-1787171794655.jpeg     From here, a progress bar will appear in the Project List area of your account if it is taking longer than a few moments to create.   jhiggins_5-1787171794440.png   If you need to cancel the workspace during it's creation progress, click on the red garbage can. This will confirm with you once more if you would like to abandon this creation. jhiggins_6-1787171794530.png       Viewing a Workspace   On the projects list, the Workspace is easily identified as an indented row under the project it was created from. Only team members invited to that Workspace are able to see the it. Each user only sees, in the project list, the name of the project the workspace was created from, and the workspaces they are part of.   jhiggins_7-1787171794813.jpeg       Inside a workspace, the project dropdown list also clearly identifies workspaces from projects.   jhiggins_8-1787171794400.jpeg         Adding sheets to a Workspace After a Workspace is created, the Administrator of it can add more sheets from the project to the workspace. If an architectural sheet, for example, becomes relevant in an Electrical workspace, it’s easy to add it to the workspace directly from the "Add sheets" button in the sheets view. Click on "Select from project". Note: Only Workspace Admins can add sheets to a Workspace   jhiggins_9-1787171794500.jpeg     You will be presented with all the sheets from the project to choose from. Select the sheets you'd like to add to the workspace and click "done".   jhiggins_10-1787171794468.jpeg       Markups and Workspaces   All markup types, tasks, photos, etc, all work the same as in a Parent Project. Please note that from a Parent Project, no markups whatsoever will be able to push down to a Workspace (and vice versa). Markups in both Parent Projects and Workspaces will only exist in their own projects. When a workspace administrator or power collaborator publishes a markup, it is only published to the workspace. It is immediately visible to the team in the Workspace Team Tab only. This allows a team working in a workspace to communicate among themselves privately, without the concern of sharing it with the overall project, or cluttering the master project documents. Task stamps inside a workspace work the same way, and holds true to the info above about staying in it's respective project type (Workspace vs Parent Project). The can be assigned, modified, added to lists, published, etc., just the same.. For more details on how the tasks tool works click here. The team inside a workspace can implement any workflow they want by making use of the tasks tool. All reporting is available inside a workspace.       Workspaces and Documents   Documents work exactly the same as sheets, if there is a need to add another document to the workspace, any workspace administrator can "Add new" and select it from the project. If an administrator clicks on the "Add new" button inside the documents tab, they will get three options: Select from project, Upload files, and Create a new folder. To select documents previously published to the project, click on “Select from project”.   jhiggins_11-1787171794460.jpeg       The documents list from the project will appear and you will be able to select any additional documents you want added to the workspace. Click on "done" once you finish your selection.   jhiggins_12-1787171794505.jpeg     If you want to create a private document inside a workspace, click on "upload files".  When a document is uploaded directly to a workspace that document becomes private in that workspace and is only available to the team in the workspace. Project documents and Workspace private documents are differentiated by the icons used. The Project documents are identified by a folder with a small building. Workspace documents are plain folders.   In addition, any document that is private to a workspace will have the “Workspace” label underneath it.  Documents can be seen, shared, downloaded from a workspace in the same way they can be from a project.   jhiggins_13-1787171794498.jpeg     If a document that was originally added to the workspace needs to be removed, the administrator can easily select it and delete it from the documents list. Deleting the document from the workspace does not remove it from the Master Project. If the document is a workspaces document - it will need to be re-uploaded to the project if needed. If the document is a project document - it can easily be re-added to the workspace following the steps listed above.       Workspaces and Team Members   Once a workspace is created, any additional team members not added during the creation of the workspace can be added using the "Add team member" button in the team page. Permission levels can be managed from the team page. Note: Only users currently on the main project can be invited to a workspace   jhiggins_14-1787171794481.jpeg       Select the team members you would like to add, and click on "done".     jhiggins_15-1787171794529.jpeg           Workspaces and Versioning Versioned sheets in workspaces will still pull from the parent project, which requires an upload that can only be done in that parent project. With sheets and versions in the workspace, any uploaded revision of that sheet in the parent project should automatically reflect in the workspace. Please assure that it has completed the publishing stage in the parent project. Aside from existing versions, new sheet numbers that do not yet exist in the workspace will need to be pulled in manually, via 'Adding Sheets to a Workspace' Show More

Our teams in the field should be able to view commitments while on the project. They should be able to see the contracted scope along with any contract values/approved change orders. It adds more work for us to save and files these into folders for them to have to thumb through to find. Show More

It would be very helpful to be able to export the current set of specifications in Build, similar to exporting as-built drawings. It doesn't make a lot of sense to be able to upload our specifications and keep them current, if we can't export a final from Build. Show More

Our company maintains a master BuildingConnected project template that includes subcontractor lists, bid packages, project bid forms, and bid package bid forms. This template is used as the starting point for all new projects to ensure consistency across our estimating and procurement teams. This makes it so we do not have to import from 3 different areas to create a new project. One limitation we have encountered is that bidder-specific Notes do not transfer when a new project is created from the template or when bid packages are imported into another project. The Notes field is not only used for project-specific information. It is also used to store important company knowledge about subcontractors that should follow the subcontractor wherever they are included in future projects. Examples include: New subcontractors that have recently reached out to our company Internal recommendations from project teams Information about who introduced the subcontractor Reference projects where the subcontractor was previously considered or used Regional office relationships and contacts Special qualifications or areas of expertise For example, a note may state: "XYZ Company reached out on 8/18/26 described the work they can do and look like a company we can consider. Send bids to test them out" If a user creates a new project from the template and XYZ Company is included in a bid package, that note should also carry over. Without the note, the team loses valuable context and may not realize the subcontractor is new to the company or understand why the subcontractor was added to the template in the first place. As employees change roles and new estimators take over projects, these notes become an important source of institutional knowledge. Today, that information is lost when projects are copied, requiring teams to maintain separate spreadsheets or manually re-enter notes. Requested Enhancement: Add an option when creating projects from templates, duplicating projects, or importing bid packages to: Copy Bidder Notes Preserve subcontractor-specific template notes Allow administrators to choose whether notes are included during duplication Business Benefits: Preserves institutional knowledge across all projects Provides visibility into new subcontractors being introduced to the company Reduces duplicate outreach and research efforts Improves consistency between estimating teams and offices Eliminates the need for external tracking spreadsheets Increases the value of BuildingConnected templates as a true company-wide knowledge base For organizations that rely heavily on templates, bidder notes are often just as valuable as the bidder list itself. Allowing these notes to transfer would help ensure important subcontractor information is available to every user and every project created from the template. Show More

Dashboards created with Insight Builder currently are only visible in Build, within the Home tool.   For Cost Management specific dashboards, we should have the ability for these to only be visible in Cost Management. It is intuitive and in some ways necessary for CM information to be in the CM product. Show More

On some projects, especially CM projects, bids are submitted directly to the Owner and not through the BC planroom.  A good feature would be the ability to turn off the bid form on those types of projects.  Thanks for your consideration! Show More

Prevent Duplicate Asset Uploads Through Automated Validation in ACC Assets Module Idea Description: Currently, when uploading assets into the ACC Assets Module, duplicate asset records can be uploaded if they exist in the source spreadsheet. While the system performs validation checks for mandatory fields such as Status, Category, Location Missing, etc and restricts uploads when these are missing, there is no validation to identify or prevent duplicate assets. Proposed Enhancement: Implement a duplicate asset validation check during the asset upload process. Before completing the upload, the system should automatically scan the incoming dataset and compare it against existing assets and duplicate records within the upload file. Expected Benefits: Prevent unintentional duplicate asset creation. Improve overall asset data quality and integrity. Reduce manual effort required to identify and clean duplicate records. Ensure more reliable asset registers for downstream processes and reporting. Align duplicate validation with other existing upload validation checks. This enhancement would be a valuable addition to the ACC Assets Module and help organizations maintain accurate and consistent asset data from the point of upload. Show More

We recently noticed an update to the Contacts section within BuildingConnected qualification applications. Previously, we were able to manually enter Harris employees as company and prequalification contacts, regardless of whether those individuals were BuildingConnected users or associated with one of our Harris entity profiles. The new format appears to only allow us to select employees who are existing BuildingConnected users. Please see accompanying Word document with screenshots. This creates an issue because many qualification applications require multiple contacts, including Safety and QA/QC leadership. These individuals may need to be listed as prequalification contacts but are not necessarily BuildingConnected users or associated with our various Harris entity profiles. Under the previous format, we could manually enter these individuals as needed. This appears similar to the recent update BuildingConnected made within the General Section – Company Address, which also changed our ability to manually manage information. BuildingConnected Support previously advised us that they were unable to change or assist with that update. Can you please confirm whether the new Contacts format is a permanent BuildingConnected system update? If so, is there any way to manually add a contact who is not a BuildingConnected user, or revert to the previous functionality? If not, what is the recommended process for contractors who are required to provide Safety, QA/QC, or other departmental contacts who do not maintain BuildingConnected user accounts? Additionally, even if our departmental leadership held individual BuildingConnected user profiles, they can only be a user on one profile at a time and we need to list the same departmental leadership across multiple Harris entity profiles and qualification applications and cannot have these contacts be tied to only one profile.  Your Autodesk Construction Cloud Case Number is : 02312105 - Ticket Resolved, but BuildingConnected support is unable to assist with the new sections format configuration.  Show More

We are beginning a new project.  My project director came to me today and asked if Autodesk could create a printable barcode for assets.  Specifically, for lighting.  This would be quite helpful. Show More

Description: Currently, the Holding Area can only be enabled or disabled globally for the entire project. We need the ability to control the Holding Area on a folder-level basis. Why this is needed: We work with external subcontractors. For specific folders (e.g., official release folders), we want to strictly enforce naming conventions. Non-compliant files must be blocked completely at the browser level, forcing externals to rename them before uploading. However, for internal WIP (Work in Progress) folders, we want the flexibility of the Holding Area so our internal team's workflow isn't constantly interrupted. Proposed Solution: Add a toggle in the folder settings that allows project administrators to enable or disable the Holding Area per specific folder or subfolder.     Show More

Currently, it is not possible to rename an incoming team in the receiving project. Duplicate team names receive a number appended to their names. When the duplicate in the receiving project is renamed/ removed, the user should be able to rename the team/ remove the number. Show More

Filter models/items by model properties Problem statement & desired action/outcome: To be able to find 3D elements object based on the parameters. Lets say the same door type have been used, but a item parameter define the fire rating of the door or door tag. The user would then like to. Please have a look at what the model viewer or Navisworks can do with parameters. This would be a good start to filter the object based on the properties. Current issue/challenges: As for now the only option is to find an element manually in the model viewer or using the find item by tag/mark on pc.  Please find the snip attached regarding filtering in desktop model viewer @membrec @Rosenthal.Tomer  Show More

From a user perspective, it would be highly beneficial if native form templates allowed images, drawings, plans, reference documents, or other attachments to be embedded directly within individual sections or chapters of the template. During form completion, users could then access these documents through an integrated viewer without having to leave the form. This would significantly improve usability, as the relevant plans or reference documents could already be linked to the corresponding section of the form. As a result, users would no longer need to continuously switch between the plan view and the form, which currently creates additional effort and reduces efficiency. Show More

ACC Review needs an option to assign default watchers/notification recipients for each discipline review template. This will automatically notify the relevant team members when a workflow is created. Currently, without notification, other team members may not see the workflow in the ACC Review tab, which can cause coordination delays. Show More

Enable seamless document transfer across Autodesk hubs and data regions while preserving version history, metadata, and document structure to simplify collaboration and document management on global projects. Show More

The current 2,000-page document upload limit can be restrictive for large project deliverables. Increasing or making the limit flexible would streamline document management and reduce the need to split files Show More

Currently, exported sheets from Build > Sheets, including issues and markups, visually display the issues, but it is not possible to identify which specific issue is being referenced. Although the exported PDF contains a hyperlink to the corresponding Forma issue, this is only useful for users and companies who have access to Forma. For documentation purposes, especially when sheets are printed, it is essential that the Issue ID is also displayed directly on the sheet. This allows users to correlate the issue shown on the drawing with the corresponding issue detail report (PDF). I am aware that the Issue Detail Report provides an option to include a sheet overview. However, the embedded sheet is only available as a reduced-size overview, and the created markups are not displayed. As a result, it is not suitable for accurately locating and identifying issues on the drawing. We require the ability to export sheets at their actual scale and size, including all visible markups and issues, with a clear display of the corresponding Issue IDs. This would ensure that users can easily locate and match issues within a PDF issue report and maintain a complete and usable project record, even without access to Forma. Below is an example of how we would like exported sheets to be displayed, including the Issue ID directly on the drawing for easy reference and documentation purposes: MichaelSaxl_0-1787116534800.png   Show More

Team, We are using Autodesk Construction Cloud (ACC) for project document management (Docs module) across our engagements. We understand that e-signature functionality is currently available natively within the Cost Management module (via DocuSign, Adobe Sign, Dropbox Sign, or SignNow integrations) for contracts, change orders, and payment applications. Our requirement is to enable e-signature capability for general project documents and PDFs (e.g., drawings, submittals, transmittals, approval sheets) stored in ACC Docs — not limited to Cost Management-generated documents. It would also be very helpful if e-signature capability could be extended to the Markups tool within ACC Files. Many of our reviewers and approvers add sign-off comments, stamps, and markups directly on drawings and PDFs during review cycles, and having native e-signature support at that stage would eliminate the need to export files to a third-party e-sign tool and re-upload them. This would streamline approval workflows for redlines, punch lists, and drawing sign-offs, keeping the entire review-and-approval process within a single platform and providing a clear audit trail alongside the markup history. Additionally, I am attaching an image with respect to the e-stamps/e-signature related ideas that were already posted in the Forma Community ideas forum for reference: Ability to Create and Manage Stamp Templates at the Project Template Level — Requests enabling stamp templates to be configured at the Project Template level so they're automatically available across all new projects, instead of being recreated manually for each one. Ability to Apply Signature/Stamp Across Multiple Pages in a Single PDF — Requests the option to apply a signature/stamp to all pages (or a selected page range) of a multi-page PDF in one action, instead of stamping each page individually.   Show More