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

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

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

We have received consistent feedback from users regarding the visibility of RFI question or answer text within Autodesk Forma. Currently, when an RFI question or answer exceeds the initial display area, users must click the "See More" link at the bottom of the question or answer to view the remaining content. This behavior can create confusion because users may not realize additional information is available, resulting in incomplete understanding of the RFI requirements. In many cases, critical context and details are hidden below the fold, and the current "See More" control is not sufficiently prominent to draw attention. We would like to request consideration for one of the following improvements: Display the full RFI question by default without requiring users to expand the text. If full display is not feasible, increase the visibility and prominence of the "See More" control by: Using a larger font size or button style. Adding a visual indicator that content is truncated. Applying a contrasting color or highlighting the control. Displaying a message such as "Additional question details below - click See More." Improving the visibility of complete RFI content would help reduce missed information, improve user experience, and minimize the risk of responses being submitted without reviewing the full question. 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

Many projects have roles such as Information Managers, Document Controllers and Project Leads who need visibility of all reviews for governance, reporting and oversight purposes, but do not need to participate in the review workflow. Could Autodesk introduce a dedicated "Review Viewer" permission that allows nominated users to view all project reviews and associated comments without being added to each workflow or requiring Project Administrator rights? Benefits: Improves project oversight and reporting. Reduces the need for elevated admin permissions. Maintains governance and segregation of duties. Allows key project roles to monitor review progress and bottlenecks more effectively. Minimises administration associated with managing review distribution lists. Show More

Around the world, lots are used to divide large projects into smaller, more manageable tasks. This approach is standard practice in international procurement, civil engineering, and commercial construction. With its packages, FORMA Data-Management offers a system for reflecting this reality. It organizes the data by assigning it to multiple packages, eliminating the need to repeatedly copy the same document into different folders. The data for these lots includes PDF, Word, and Excel documents, models, and, of course, floor plans. Which easily change after the contract has been signed in any project. Problem: Watchers are not automatically notified of these changes, even if the package status is set to “(current version).” Impact: An architect ( can't overwhelm all contractors with the same big data all the time. Information must be split and sorted and brought to the right contractor) So he must now manually notify the 30 different contractors in one project of every change in their lots(such as new versions, indexes, or other attributes) to the documents. Or they must delete the same drawings from the package and add them again, which takes a lot of time for each file.  Solution: We need a notification system that informs watchers not only about the package attributes themselves but also about updates to the package’s contents. Dear Autodesk Team, please ensure that changes to the package’s contents automatically trigger a notification that informs about the actual change. @christoph.grossmann  Show More

The Image that would appears in the Project Invitations emails is the one Loaded in the Hub Admin Settings section, meaning that all the projects invitations from project within that Hub, would have that image. At the moment, the Project Logo image in Project Seettings is not the one appearing in the email invitation and its appears in the project thumbail list in your Projects page in Autodesk Forma.   Suggestion Idea: the logo configured within the Project Settings should represent the specific project and therefore should appear in project-related invitation emails. When a user receives an invitation to join a project, displaying the project's logo helps identify the project immediately and reinforces project branding.   In contrast, the image configured under Hub Admin Settings is a hub-level branding element that applies across all projects within the hub. Therefore, it would be logical for this image to be used in hub-level communications, such as invitations sent directly from the Hub Admin, rather than in invitations related to individual projects.   For organizations managing multiple projects within the same hub, using a single hub image for all project invitation emails can create confusion, as recipients cannot easily distinguish between projects from the email branding alone.   Could you please re-evaluate this behaviour with the product team and advise whether:   This is the intended design and cannot currently be changed. There is any alternative configuration that allows project invitation emails to display the Project Logo configured in Project Settings. This is a known limitation that is planned to be addressed in a future product enhancement.   I appreciate your assistance and look forward to your feedback. 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

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:   Show More

Review markup is currently limited to viewable file types (PDF/models). Add markup/comment support directly on Excel files within a review, without converting to PDF first. Show More

Revision/transmittal numbers currently must be added manually via attributes, which is time-consuming and error-prone. Automatically include the current review ID and current transmittal ID as file metadata/filename info, similar to how file versions display, so reviewers can see status directly from the Files module. Show More

A recent update in the Review Workflow Settings allows users to assign Key Reviewers within the review interface. However, the "Minimum Number of Key Reviewers Should Review" option is currently available even when the workflow is configured as "Every Key Reviewer Must Review". This behavior appears to be a bug or configuration error because the minimum reviewer count is not applicable when all key reviewers are required to complete the review. Having this option available creates a workflow inconsistency and may lead to incorrect review completion behavior. Expected Behavior: The "Minimum Number of Key Reviewers Should Review" option should only be available when the corresponding workflow condition supports minimum reviewer selection. "Every Key Reviewer Must Review" is selected, the "Minimum Number of Key Reviewers Should Review" option is still available. If the system is designed to support this option in this workflow type, then the configured minimum number of reviewers should be respected and function correctly when reviewers are added through the review interface. Please investigate this issue and implement a fix to ensure the workflow settings are aligned with the intended review logic. Show More

Operating as a global company requires access to multiple currency types within a Bidding and Sourcing Platform.  The following currency types are missing from Building Connected which is limiting our ability to successfully utilize the application.   Missing Currencies Needed in BC CRC ₡ – Costa Rican Colón CHF Fr – Swiss Franc GBP £ – Great British Pound JPY ¥ – Japanese Yen CNY ¥ – Chinese Yuan KRW ₩ – South Korean Won TWD NT$ – New Taiwan Dollar THB ฿ – Thai Baht VND ₫ – Vietnamese Dong SGD $ – Singapore Dollar IDR Rp – Indonesian Rupiah MYR RM – Malaysian Ringgit RUB ₽ – Russian Ruble PHP ₱ – Philippine Peso     Show More

It's great that we can now add Custom Fields in Submittals, but we need the option to set the custom field as Required, like in the Issues tool.  We also need the ability to choose which Submittal Type a custom field is added to. Show More

Currently, when we create a non-member to receive a correspondence, to user remains forever in the "non-members" list. We should be able to delete that. Show More

Choose whether to keep, hide, or remove markups when uploading a new version. This would result in clearer and cleaner reviews. Show More

Notify users before closing a review if there are any unpublished markups. This prevents information loss. Show More

Presently only Issue Reports support template-based scheduled exports. Extend the same scheduling capability to Review, Files Log, and Transmittal reports so recurring status updates go out automatically. At present, the functionality is limited to the Data Connector. For project-specific requirements, direct integration with Forma would add significant value by automatically fetching relevant project data. This would not only save time but also improve data accuracy, enhance workflow efficiency, and reduce dependency on manual update. Show More