Problem Statement When a Navisworks model is exported to NWD with certain elements hidden, and that NWD is imported into Autodesk Forma ACC, the hidden elements are not imported at all. They are missing both from the 3D view and from the model/construction tree, and cannot be recovered by any visibility control inside the ACC viewer Autodesk Support confirmed this is expected/current behavior in BIM 360 and Forma (Support Case No. 26217856): hidden elements are simply not translated into Forma, with no supported workaround available at the ACC level. We isolated the cause by exporting the same source model twice With some elements hidden → all of the hidden elements are missing from ACC With everything unhidden → the full model imports with no missing data. This confirms the missing-data pattern tracks exactly the hidden/visible state of each element at export time, not transparency, file structure, or import order maxence_dugourdPAS6T_3-1786974791101.jpeg maxence_dugourdPAS6T_2-1786974776762.jpeg Proposed Enhancement Treat the Navisworks visibility state (shown/hidden) as a display attribute carried into Forma, the same way Navisworks itself treats it, not as an exclusion filter applied during translation. Hidden elements should still be imported into the ACC CAD Viewer and listed in the model tree. Their default visibility in ACC can be "hidden" (matching the source), but they should be togglable through normal ACC visibility controls, exactly like elements that were visible at export. We understand that Autodesk Platform Services' Model Derivative API already supports this via the advanced.hiddenObjects: true parameter on translation jobs (POST /modelderivative/v2/designdata/job). We would like this option, or an equivalent, exposed as a supported setting for ACC/Forma NWD imports, ideally configurable at the project or workspace/hub level, rather than being limited to custom APS integrations built outside Forma's own pipeline. Business Impact Enables publishing the exact same NWD used for Navisworks directly to ACC, without a dedicated "unhide everything" reprocessing pass beforehand. Removes a recurring, error-prone manual step from every model publish Lets teams keep specialist or advanced content hidden by default for the general project audience while still making it available in ACC when needed     Show More

Right now "Border Color" makes sense only for things like Text, where it literally set the color of a border around the text box, but it also controls highlighter color, pen color, and line element colors, none of which have borders. I find the box around the text is usually sized wrong and is in the way, so I set it for transparent, but then my pen and highlighting also is "transparent", even though it draws as a thin gray line. I propose making this just "Color", and it sets all the colors: lines, pen, highlight, text, shapes. You want all those things to have color. Text boxes do not need borders around them - you can already draw a cloud or box around your text if you want it, but it just makes the color control confusing. What would be best is if each tool had its own persistent color selection, but that's harder to implement, I'm sure, and I'd be happy to just make "Border Color" into "Color" and control the text color and everything else. Show More

When opening ACC Model Coordination content in Navisworks Manage, it is loaded using Shared Coordinates by default and is not immediately visible. Users must manually navigate using the ViewCube, switch to Plan View, use Zoom Extents, or create a Perspective View to locate the content. In contrast, Revit-to-NWC exports allow coordinate control (Shared Coordinates or Project Internal Coordinates), and using Project Internal Coordinates makes the content visible immediately. ACC Model Coordination currently does not appear to provide a similar coordinate setting, resulting in additional user effort, confusion.We would like confirmation on whether this is the intended behavior and whether a workaround or coordinate control option is available or planned. 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

"Share with projects" is a extremely useful tool in Insight Builder. Customers can publish insights in all / selected projects in seconds! Currently only permissions by role are available, and it would be useful to manage permissions by "company" to manage the information shared with the stakeholders/suppliers. For example: GC can have internal Health&Safety dashboards that cannot be share with the "safefy subcontractor team" or control the info shared with the final client. Show More

Would be great to get hourly or daily summary of bids submitted etc in Building Connected. or at least have the option Show More

Right now if we create a proposal/submit a bid for a subcontractor the system does not send notifications which is concerning because the whole team isn't aware a bid has been uploaded. Show More

Currently, checkboxes across modules require users to manually select items one by one. There is no ability to select multiple items at once using intuitive shortcuts like Shift‑click (to select a range) or Ctrl/Command‑click (to select multiple non‑contiguous items). This makes workflows involving dozens or hundreds of selections extremely time‑consuming and inefficient. Show More

Currently, asset markups on Sheets do not provide visibility into Systems. Users cannot filter markups by system or easily identify which assets belong to a system. This limits the usefulness of the Systems feature and prevents a full‑circle workflow where system associations are visually represented on Sheets. Show More

Currently, markups in ACC Build must be made much larger before they can be moved with a finger or iPad pen. This adds unnecessary steps to the markup process and slows down workflows. The limited responsiveness of shapes and tools creates frustration for users in the field, making document markup cumbersome and inefficient. Annoyances like this hinder adoption of ACC Build. Show More

Currently, when looking at file under Files, we can't use the continuous scroll option and edit the file in question at the same time. This makes it difficult to edit a document efficiently. It would be beneficial to be able to do both at the same time.  Show More

1) Keep the same template and nomenclature for the data shown when extracting summaries of RFIs, Submittals and Issues in excel format. Currently, submittals will show Ball in court under a certain name, but RFIs summary will present it differently which makes it difficult to follow up with the concerned parties about all their due tasks.    2) A master summary of all Submittals, RFIs and Issues that can be extracted as a PDF or Excel would be really beneficial. Show More

Currently, when using Build on an Ipad, functionnalities are limited which makes it hard to manage submittals, RFIs, Sheets, etc while being on site and working from an Ipad.  Show More

Currently, markup options for photos are very limited. Users only have access to a simple freehand drawing tool, with no ability to insert shapes or text. Markup is also restricted to mobile devices, leaving web users without functionality. Additionally, there is no option to automatically stamp photos with metadata such as date, time, or GPS coordinates. These limitations drive users outside of the platform to annotate photos, which reduces adoption and efficiency. Show More

When uploading new sheets on Forma Build in the sheets section, it would be really helpful if we could select the area for the software to look to help it autofill the sheet's title. Sometimes Build doesn't read the correct sheet title and writting them all one by one is very long and tiring.  Show More

Currently, view settings for assets are not retained once a user clicks on a category. This forces users to reconfigure their preferred view every time they navigate, which is tedious and inefficient. For workflows that rely on consistent views, this limitation disrupts productivity and reduces usability. Show More

Currently, when opening an Issue on an iPad, users must click on the small comment box in the corner to see if comments exist. There is no quick way to identify or view comments directly from the main Issue pane. This makes it easy to miss important context and slows down workflows. Since comments are one of the most valuable collaboration features in ACC Build, limited visibility reduces their effectiveness. Show More

Currently, when referencing forms to assets via the popup window in the Assets module, users cannot rename forms directly. To rename a form, they must open it fully, which is time‑consuming and inefficient—especially when managing projects with thousands of assets and multiple forms per asset. This slows down workflows and creates unnecessary friction.   Proposed Solution Add the ability to rename forms directly from the popup window when referencing assets. Provide a simple inline edit option (e.g., pencil icon or right‑click menu). Show More

Currently, static UI elements such as Asset Categories in the Assets module take up a large portion of the screen with no way to collapse, resize, or adjust spacing. This reduces the amount of usable space for viewing asset details. Compared to BIM 360 Field, Build displays less information on‑screen due to these fixed UI elements. Users frequently request more flexibility to maximize their workspace. Proposed Solution Add the ability to collapse, minimize, or resize static UI elements such as Asset Categories. Provide expand/collapse toggles for panels to free up screen space. Allow users to adjust spacing or hide panels temporarily for a cleaner view. Show More