Within the transmittal tool we face the issue that the displayed "Folder path" hyperlink is not updating, nor is there a indicator once a file is moved to an other folder after the transmittal is created. We understand that the transmittal is designed to snapshot the data at the exact moment of creation. And we won´t change this behaviour as it becomes so often important to clearly show what was exactly sent out. But  we would require at least an indicator next to the folder path if the file was moved to an other location after the transmittal was created. Similar feature is already designed if the version is updated or if the file from the transmittal is deleted on Forma Files. Then for those attributes a orange circle appears giving the people who are part of the transmittal a quick overview that there is a updated of the files they have sent out / received. But some how for the folder path this wasn´t designed by Autodesk yet.  The current behaviour if the file is moved is following. The link is still working and directs you either to a empty folder or to a folder with so many files that you need to search for it and you will not find the file in this folder. Then you need to investigate if you have made a mistake by searching for this file in the folder where you linked by the displayed path until you recognise that the original file is moved.    The next thing is if you select the moved file and than click on "File activities" you will see in the history the reference to the relevant transmittal and if you click there on the link you will redirected to the correct transmittal even if the file is moved.  Question why does it work in this way but not the other way round???    Our proposal for this issue is following: Please add at least a indicator to the folder path, once a file is moved, similar as it is for the version or if a file is deleted. So that all participants of the transmittal easily know that the files location is changed. Next step would be that there indicator e.g. contains the link to the new folder path. This ensures, on the one hand, that the status quo at the time the transmittal was created is preserved, and, on the other hand, that all the intelligent features promoted by Autodesk are available, allowing you to jump to the correct file location at any time and, if necessary, easily access the latest information and all attributes and details assigned to the file—such as additional indicators, which are not displayed in the transmittal.     Show More

In many implementations—especially for owners and projects operating in controlled or audited environments—there is a need to allow users to view documents and create/publish markups, while still restricting the ability to download files. Currently, “Publish Markup” is tied to download permissions. This creates governance challenges for organizations with strict data control policies, as it increases the risk of unintended file distribution. This scenario is common when multiple external stakeholders are involved in document reviews, but ownership and distribution of source files must remain tightly controlled. Proposed Improvement: Enable a separate permission setting that allows users to publish markups without requiring download access. Why this matters: Supports stricter data governance and compliance requirements Enables secure collaboration with external stakeholders Aligns with real-world deployment needs in controlled environments Community input: If you have encountered similar challenges or believe this capability would add value, please vote for this idea or share your use case to help demonstrate its impact. Show More

Quick suggestion: In Sheets, could we add a 'Save as Default' option for issues filters? It would be great if users could choose to keep 'Closed' issues hidden by default, so they don't have to toggle it every time they log in. Might be a nice quality of life improvement for the team~ thank you! Show More

Currently, uploaded reference photos are displayed at a fixed size for whole report, which can limit their readability. It would be valuable to allow users to resize reference photos by either enlarging or reducing them. This would provide the flexibility to: Enlarge images when greater detail and visibility are needed. Reduce image size to optimize the overall report layout and fit more content on a page. Giving users control over the display size of reference photos would improve both the readability and the presentation of generated reports, allowing them to tailor the layout to their specific reporting needs. Show More

Problem statement: We identified a behavior difference between BIM 360 and Forma/ACC regarding model orientation in the viewer. The same model can appear with a different rotation depending on the platform. In addition, “Reset Orientation” currently has no visible effect in Forma/ACC, while it previously worked as expected in BIM 360.   Current behavior: The platforms apply model transformation metadata differently: In BIM 360, transformations are not applied using LMV applyRefPoint . In Forma/ACC, all clients use applyRefPoint=true . This explains why the same model can appear rotated differently between BIM 360 and Forma/ACC.   Impact: This creates confusion for teams migrating from BIM 360 or comparing models across platforms. It can affect coordination workflows, saved views, issue locations, and model reviews.   Desired outcome: Improve the Forma/ACC viewer so model orientation is consistent with BIM 360, or provide a clear user-facing option to control/reset orientation when metadata transformations are applied. The Reset Orientation command should have a visible and predictable effect in Forma/ACC.   Business value: This would improve viewer consistency, reduce troubleshooting and support cases, and make migration from BIM 360 to Forma/ACC smoother. Show More

Current Situation: In the ACC Forms module, the Location field under Basic Details is optional. As a result, forms are often submitted without a specified location, leading to incomplete records and difficulties in tracking, reporting, and assigning corrective actions.   Requested Enhancement: Make the Location field mandatory in the Basic Details section of all forms, or provide an administrator-level setting that allows organizations to configure the Location field as mandatory.   Business Benefits: Ensures consistent and complete data capture. Improves form traceability and audit readiness. Enhances reporting and filtering by project location. Reduces data quality issues caused by missing location information. Supports better coordination of site-based inspections, observations, and corrective actions.   Suggested Solution: Add a configuration option in Form Templates such as: Location Field = Mandatory / Optional or A project-level setting that allows administrators to enforce mandatory location entry before form submission.   Use Case: For quality, safety, and inspection forms, location information is critical for identifying where an issue occurred. Mandatory location entry will improve compliance, reporting accuracy, and operational efficiency. Show More

Autodesk Forma Build FORMS We would like to suggest the addition of a dedicated permission level for the Form Toolin Autodesk Forma Build. Currently, the RFI Tool includes a permission setting that allows users to be assigned a “Manager” role, and the Submittals Tool similarly provides a “Submittal Manager” role. Introducing a comparable “Form Manager” permission for the Form Tool would ensure consistency across these modules. Without this functionality, we are required to grant broader Project Administrator access to team members in order to manage forms, which is not ideal from a workflow governance and access control perspective. We believe that adding a Form Manager role would enhance usability, improve role clarity, and support better permission management within projects. Show More

In the Form Detail Report, text displayed within complex tables is currently too small, making it difficult to read in the generated report. It would be beneficial to increase the font size used in tables and/or improve text wrapping to enhance readability. Better formatting would make table content easier to review without compromising the overall report layout. Improving the readability of table content would result in clearer, more user-friendly reports, especially when tables contain detailed or extensive information. Show More

In Forma Takeoff, it would improve estimator efficiency if there were a way for them to cycle through drawing sheets in a given Takeoff Package by using the keyboard. On the keyboard, Tab, PgUp/PgDn, arrows or numbers would all be suitable methods of navigating to the next or previous sheet in a drawing set. The dropdown menu located at the top of the screen is generally okay, but it ultimately requires more sheet navigation time from the estimator. Especially on large projects, the cumulative effect of these repetitive micro-delays can negatively impact the overall estimating efficiency. Thank you! Show More

We have a couple different use-cases where we have hit the maximum of 50 "additional line items / outputs" currently allowed per Takeoff Type.  Increasing the maximum to 75 or 100 would allow much greater flexibility with being able to do different types of estimates.   Also, the ability to do a custom sort or at least sort the "additional line items / outputs" by classification would be extremely helpful.  Currently they are just displayed in the order they are added to the Takeoff Type. Show More

Hello Dev Team, 1 . Default grouping of projects by Hub :  Current situation On the home screen, each row currently represents a single project, regardless of its associated hub. When users are working across multiple hubs and projects, this results in long, flat lists that are difficult to navigate, even with filters. Proposed improvement Introduce a default grouping of projects by Hub, with a collapsible structure: Each hub appears as a parent item Projects are nested within the hub Clicking on the hub icon expands/collapses the project list This behavior already exists in Forma Site Design project pages, where projects are grouped by hub. 😍   Expected benefits Improved readability of the home screen Reduced cognitive load when navigating large environments Faster identification of the correct project context Better alignment with how users conceptually organize their work (hub = environment, projects = content)   2- Filtering by Module (in addition to Hub / Title / Date):  Current situation The filter system currently allows filtering by: Hub Title Date However, users often work across multiple modules (e.g., Site Design, Building Design, Docs, etc.), and this dimension is not currently available. Proposed improvement Add a filter by module in the filter panel.   Expected benefits Faster access to relevant projects based on workflow Improved efficiency for users working across several modules Better support for role-based usage (e.g., designer vs BIM manager) More scalable filtering as the Forma ecosystem continues to expand Regards Olivier     Show More

In the Submittals workflow, steps are labeled as "Step 01–n," which makes it difficult to understand what each step represents. This creates confusion among project members and increases communication overhead. Requested improvement: - Allow custom labels for each workflow step Example: - Step 1: Internal circulation due date - Step 2: Internal approval - Step 3: Client submission Custom step names would make workflows much clearer and easier to manage, especially for teams with multiple stakeholders. Show More

Idea : Request to introduce a Return/Reassign to Previous Step function for Forms utilizing the Section Assignee workflow.   Reason : This enhancement has been identified as an essential feature to effectively manage Forms within the assigned responsibilities of each Section Assignee. Currently, once a section is completed and submitted to the next workflow step, the previous assignee no longer has permission to edit their submitted section. During the subsequent review, the next assignee may identify errors, missing information, or require amendments to the content or attachments submitted in the previous step. However, as the previous section has already been submitted, the original assignee is unable to make the necessary revisions. This often results in inefficient workarounds or the need to recreate the form. Implementing a Return/Reassign to Previous Step function would allow the current reviewer to send the form back to the relevant previous assignee for amendment while maintaining workflow control, accountability, and the integrity of the Section Assignee process. This enhancement would significantly improve collaboration, reduce rework, and streamline the overall form review and approval process. @dgkusuzeyaziante @irhamhameeda_idris @armilahlasemang  Show More

I recommend adding the ability to attach photos or PDFs to form templates that can be utilized as reference documents while completing the form. An example would be monthly safety inspections where diagrams are utilized to identify different components of the safety equipment that needs inspecting. This would be crucial for mobile users as there access to reference documents are limited in the field. Show More

Better mouse controls when creating locations and 2D assets outlines. Currently if you push the scroll button on the mouse, as it is intuitive when you wnat to move the view, the whole shape moves. The idea is to have this intuitive behavior and the shape shoudl stay in place.  Show More

Markup lines in the Change Management tool default to being Budget Only lines. There are many kinds of markups that would not be Budget only, like insurance or bonds. There is no way to change this default. There should be a setting associated with the Budget Code or with the Markup Template that allows for customization of this setting.   In my mind, it would be best for the Markup lines of a Change Event would be able to match the Scope of the Change Event itself.  Show More

I am unable to fully utilize Autodesk Forma on my projects because of the 250 character limit on folder structures. We consistently receive client and partner files that exceed and are unable to share and upload. Is there any plan to correct this in the future to more closely align with industry standards like Procore, Dropbox, etc? Show More

In Cost management in Cost payment applications, there is an option to export/import template available, currently the template has fixed columns and after downloading there is not column to input quantities when claiming the current period work completed, in India Cost per unit and amount of a SOV line item remains fixed, unless a Change order is created, so in payment applications import/export template its important to have Quantities column(editable) along with un editable columns of unit cost and amount.  Show More

Hi all, Since the latest update, newly created reviews are visible only to users participating in the review process or to project administrators. Therefore, there is an urgent need to introduce a Watcher role.   As this functionality already exists in the Submittals tool, it should not be too complicated to integrate it into the Reviews tool as well. Thank you for your attention to this matter. Show More