Within Autodesk Construction Cloud (ACC), there is currently an inconsistency between Files and Specifications with regard to access control and auditability. Files Clear separation between View and Download permissions Download actions are logged via File Activities Specifications No distinction between View and View & Download When a PDF can be viewed, it can always be downloaded No available logging to identify if or when a document was downloaded This results in a governance and auditability gap, especially since Specifications often contain contractual, technical, or sensitive project information. Requested enhancement Introduce a View-only (no download) permission for Specifications, similar to Files Add download logging / audit trail for Specifications This would improve consistency across ACC modules and strengthen governance, security, and traceability without impacting existing workflows. Show More

When you are creating a new Issue (currently) you can only search the "Type" field to find the issue type.  Safety, for example, may have a long list of Categories and Types (in our case, we have over 40 categories & 250 types). Scrolling is not your best search option. In that case, word search is the quickest option.   It would be helpful for there to either 1) be a Category field that when selected, reduce the Types to just those Types under that Category or 2) the search box to also search the Category. For example, if I have a Safety category called "Safety - Excavation/Trench" and a type called "Trench Box", if I type in "trench" into the search box, it will only show "Trench Box" but my issue doesn't involve a trench box so now I would have to back out and either word search a different word or scroll. From a setup standpoint, we would have to add the Category to every type in order for it to be searchable so that all options show.  Show More

It would be very helpful to have more editing and formatting options for ACC meeting PDF exports. At the moment, repeated footer text and system‑generated information cannot be adjusted or removed, which reduces the clarity of the documents. Additional controls for layout, spacing, and footer content would ensure that the PDF is already clean and well‑structured without needing further editing in an external PDF tool. Show More

Summary Please extend the Autodesk Forma Issues API "Issue Placements" beta to support placing issues on Sheets (the published 2D drawing set), not just 2D files and 3D models. We need third-party and field-capture tools to be able to write an Issue's x,y pushpin position onto a Sheet through the API, so the pin shows up in the Forma Build Sheets/drawings experience exactly where it was captured. The workflow we need Our team captures issues in the field using OpenSpace. Those issues sync into Forma Build with their title, description, photos, and metadata — but they arrive WITHOUT a location pin on the drawing. Someone then has to manually re-place each pin on the correct Sheet, which doesn't scale and defeats the purpose of capturing the location in the first place. What we're asking for We understand the new Issue Placements beta already lets applications create, read, update, and delete issue pins on 2D files and 3D models. We're asking Autodesk to add the same capability for SHEETS — i.e. allow an API client to create/read an Issue with a pushpin and x,y coordinates tied to a specific published Sheet, so the issue appears pinned in the Forma Build drawings/Sheets module. Why it matters - Location is the whole point. An issue without a pin on the sheet is just a to-do item; an issue pinned to the exact spot is actionable for the crew. - It closes the loop between field capture and the office's source-of-truth drawings. - It removes hours of manual, error-prone re-pinning on every project. - It lets the field tools our teams already use deliver a complete, automatic experience inside Forma Build. Impact 2 / 3 Page 3 Our field teams log a high volume of issues every week. Automatic sheet-pinning would save our superintendents and engineers significant time on every project and keep our drawing set as the single source of truth. OpenSpace's development team has told us they are ready and willing to dedicate engineering resources to building this integration as soon as the API is available. Thanks for considering this — happy to be a beta tester for Sheet placements. Show More

We would like the functionality to mark an entire section as "N/A" instead of having to mark each question as "N/A"  An Example of how we would use this:   On our Daily Safety Assessments we have sections where if the hazard isn't present on the Jobsite  - ex confined spaces,  we don't need to assess any confined space requirements. We still have that on our inspection form, so we end up marking all of the questions as "N/A" Having the ability to mark the entire section of Confined Space section as "N/A" would save alot of time and clicks. This applies to all of our forms- the safety example is just an example.    Show More