I manage two separate companies on Building Connected.  It would be useful to export one company's Do Not Use List to import it to the other.  Additionally, exporting a list would make it easier to use excel's tools to mine that information.   Best, Jon Hanlon Show More

Currently assets need to be tagged manually with no way to do it automatically. For light fixtures tagging each fixture can take hours given the size of the project. It would be nice to have a feature that will recgonize assets on a sheet and automatically tag them for tracking. Show More

The temperature is in Fahrenheit in homepage of build module. Can you add an option to switch to °C ? Show More

When an RFI, Submittal, or Issue is overdue, Autodesk should have automatic email reminders sent out to whoever has the ball in their court. Procore has this where an email is sent daily. Show More

There should be an option to automatically publish markups, like lines or shapes, that I draw on sheets in Build. Having to publish each one manually is a huge time-waster. Show More

Currently, in the Model Coordination, clashes are no longer displayed as clashes once a task has been created for them, even if the task is still marked as open. This is incorrect in practice and leads to confusion, because clashes remain clashes until the task is completed/closed. The clashes must remain visible until then.   Perhaps instead of directly "closing" the clashes, a clash status could be introduced: open, in progress (once a task is created), and completed/closed.   Show More

When creating a new RFI, some fields are required, marked with an asterisk, and many are not. Can we please allow admins (RFI type creators) to remove/disable fields that are not required? It is causing confusion amongst the team, and we want to streamline, simplify and clarify the process for the project. Similarly, can we be given the option to choose which ones are required, this could be a tick box after each item inside the RFI type (template). Thanks! Show More

Possibility to bridge issues between ACC projects. This would save time working in projects where you have multiple ACC hubs for the same project. For example client, designers, and main contractor each have their own hub. Show More

In Build Sheets, photos attached to Sheet annotations should be sortable. Requested features: Sorting by name, capture date, upload date, uploaded by, etc. Consistent sorting in annotation view and photo reference panel. This would greatly improve site documentation, making photo management faster and more transparent. Show More

Users (especially the consultants) would like the ability to flag each submittal item with indicators for Cost Implication and Time Implication. Currently, ACC Submittals does not provide dedicated fields for capturing these impacts, making it difficult for project teams to assess potential variations or schedule risks early. This feature request proposes adding two optional columns—Cost Implication and Time Implication—as configurable Boolean or dropdown fields at the submittal item level. This enhancement would help stakeholders quickly identify submittals that may affect project cost or schedule and support more efficient decision-making, reporting, and risk tracking. Show More

Every GC has a specific Submittal Stamp that we use to acknowledge general conformance review for all submittals going to the design and engineering members of a project.  Currently, every Project or Account Admin needs to create that standard stamp from new, for each new project.  It would be great to add this to the Project Admin Template Setup settings.  Thank you! Show More

Please add a means to lock the Asset markup boundaries. Either create a ‘Lock Asset Mappings’ setting that Project Admins can set or, as with Location mapping markups, allow only Project Admins to add and update the Asset markup locations. Too often the people in the field are accidentally moving the Asset markup boundaries. These users require the ability to create and publish markups, so removing that Sheets permission from them is not an option. Show More

It would be nice if we are able to give a specific role or individuals the permission to add members to a project without being a full admin. We foresee many instances where we would want someone assigned to managing a project to be able to add new members to the project, but want to avoid giving full admin access to that project. This would allow us to isolate these permissions and have a better workflow for adding people to projects where their involvement is needed based on the current status of the project. Show More

Many companies use nested links, and when bridging projects the nested links in a main model do not resolve their pathing when received by an external company so they do not display.  Please allow nested link paths to be able to auto-resolve when using Bridge. Show More

Provide the ability to reference and Asset to an Asset.   I have a client who’s an insurance restoration builder using Assets as locations within Autodesk Build. This approach allows them to reference nearly any project element to a specific location, enabling detailed tracking of the remediation lifecycle for each space. They can't however reference a physical Asset to that space.   While it may seem logical to use Locations, their visibility is limited to Issues, Forms, and Assets once the Location field has been populated, with no visibility across other Autodesk Build items. Furthermore, unlike Assets, QR codes cannot be generated directly from a Location, necessitating the use of third-party tools.   Alternatively, enhancing the functionality of Locations could address this. Show More

It would be useful for project admins or those with relevant permissions to be able to subscribe to a folder on behalf of selected users, roles or companies. As notifications can be sent for users who subscribe to a folder, many users (particularly field teams) will not subscribe to a folder, as this is not possible using the ACC mobile app.   Additionally, if in app mobile notifications were possible,  this would enhance the experience more. Show More

Who is allowed to do what is a big concern and often permissions must exceed what would be wanted for a particular user in order to grant access to one or two features they need, but then overextends their access to other features.  The ability to add users to a project (and thus to the Account members) is something that can get out of hand quickly and there is no way to track who added a user. It would be terrific if the Members Report could include who the user was added by.  This would go a long way in helping us maintain order within the system.  Show More

I would like to see Reviews moved to the Build side. All my reviews need to be done in a single area. Reviews (internal review, subs, designers) then it can be moved to RFI/Submittals to be sent to the owner. Show More

It would be good to see customizable reports and print this out. For example, Reports for Forms can go for about 10 pages but can be consolidated to 1-2 pages.       Show More