When adding new users on the ACC or BIM360 platforms, it is necessary to add them individually by logging into each project. In the account management section, we request the creation of a dashboard structure where users can be assigned to projects in bulk (by ticking them). Do you have any alternative methods to simplify this process? Show More

The ability to control, remove, and/or favorite projects in the project list on the home page. Each person should be able to toggle on or off projects to reduce their list. Show More

This has been raised several times, but it never seems to gain much traction—which I find quite surprising! We urgently need the ability to add members to multiple projects at once. We manage over 100 projects, and every time a new starter joins, I have to manually go through each project to: Select project → Add members → Add user → Send invite — repeated 100+ times. This process can take over an hour. To make matters worse, the new starter then receives 100+ email notifications, which is overwhelming and unnecessary. It would be incredibly helpful if ACC allowed us to: Add a company or group to multiple projects at once, or Assign a user to selected or all projects in bulk. This would save a huge amount of time and reduce email clutter for new team members. Show More

We’ve identified several challenges when working in external Autodesk Construction Cloud (ACC) portals where our team members are added as collaborators or share data via Bridge. These situations often result in reduced visibility and control over company data, permissions, and intellectual property. When a Revit model is published, regardless of whether certain elements such as legends, views, or schedules are excluded any user with download rights to the folder containing that published version can still download the source file, which includes all excluded information. In external portals, where administrative control lies with another organization, this creates significant risk. To maintain control, we would need to negotiate that all versions of our Revot models remain “view only” for any non-EDGE participants. However, this approach is both impractical and unenforceable in real-world collaboration scenarios. Additionally, it appears that within these external environments, folders may exist that contain our models but to which we have no visibility or permission control. Without a mechanism for the originating account to maintain oversight. ACC’s use as a Common Data Environment (CDE) is undermined by the lack of intellectual property protection. Below are a few ideas and suggestions that could significantly improve administrative control and data security in these cases. Admin Visibility into External Projects When a user from our organization is added to an external ACC project, account administrators currently have no visibility of these connections. Suggestion: Allow originating account admins to automatically view or report on all external projects their users are participating in. This would support oversight, compliance, and lifecycle management of shared data. Control Over Data Created on External Portals When our staff create workshare Revit models on an external portal, that data effectively becomes controlled by the host project’s admins. Suggestion: Introduce an option for the originating account to retain “ownership” or administrative oversight over any data created by its users, regardless of the hosting account. Administrative Permissions over Bridged Data When Revit models are shared through Bridge, the original creator loses admin rights over their data once it enters the external environment. Suggestion: Allow the originating account to retain administrative permissions over bridged data by default without requiring admin rights within the recipient’s portal. Restricting Download of Source Files Currently, users with download permissions on a published model can also download the source Revit file, even if only specific views were published. Suggestion: Disable “Download Source File” by default for anyone outside the originating company unless explicitly permitted. Ensure that any published model available for download only contains the content intentionally published, not the entire model or embedded IP. Data Lifecycle and Archiving Once a project is complete or access is removed, there’s limited ability to recover or archive the data that was hosted externally. Suggestion: Introduce tools or automated workflows that allow the originating account to archive, back up, or retrieve its content at project closeout for projects hosted outside the organization’s own portal. Regards, Steven Eadie BIM Manager | Edge Consulting Engineers 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

Hi There,   Not too sure if this has been suggested before, but it would be beneficial to extend the front-end search capabilities of projects using project meta-data such as address and extending filtering options with project meta data as well.   Thanks and much appreciated Show More

Our team has encountered a serious issue within Autodesk Construction Cloud regarding submittal revision control. Once a new revision is created, there is no functionality to revert or step back to a previous revision. This limitation presents a major risk and operational failure for our project. In cases where an incorrect file or action is submitted, there is currently no way to correct or undo that revision. This is absolutely detrimental to our document control process and is causing confusion, delays, and potential noncompliance with our QA/QC standards. At minimum, we need one of the following options implemented or confirmed as feasible: • The ability to revert to a prior revision or • An administrative override to remove or replace an incorrect revision without corrupting the revision history. Please escalate this concern to the appropriate technical and product management teams immediately. This is not a minor inconvenience — it’s a significant workflow gap that undermines Show More

Even though we have Watcher's field in the Issue detail, when we extract the report, it's not appearing. Even in the template field list watcher field is not available  Show More

When adding a new company in ACC, it would be helpful to have an additional field for an “Alternate Name” or “Trading Name” alongside the existing “Company Name” field. In Australia (and many other regions), it’s common for organisations to have a registered legal name that differs from their trading name. On most projects, the trading name is what users and stakeholders recognise and use on a day-to-day basis. Currently, ACC only allows entry of the registered company name. This can cause confusion when teams search for or select a company during transactions such as RFIs, Submittals, Forms, or Issue assignments, because they often look for the trading name used on site. Suggested Enhancement: Add an optional “Alternate Name” or “Trading Name” field in the company setup form. Allow both names to appear in search and selection menus (e.g., “Registered Name (Trading Name)” format). Ensure both names are searchable throughout the platform for clarity and ease of use. Show More

Currently, when a user with a default role (e.g., "Project Admin") creates a new project, their role is not automatically applied to the project they created. Instead, they must manually assign their role after project creation via "Project Admin > Members". This behavior differs from when the same user is invited to a project by others, where the default role is automatically applied. We believe that automatically applying the default role upon project creation would improve user experience and reduce administrative overhead. Please consider implementing this feature to ensure consistency and efficiency in role management. Show More

To maintain data integrity, we want to avoid project number duplication. During project setup, can we enforce a requirement for a unique project number to prevent duplication across projects? Please advise. Show More

  Add a permission setting to restrict project admins so they can only add members that already exist in the account directory, managing all members from an account level   problem: compliance, security, cost control, data governance. impact: risk of unapproved users gaining access, audit issues, billing surprises.   Show More

Add Autodesk account activity logging so account admins can see all admin activity at the account level. Show More

Hi all,   Today, I’d like to discuss my suggestions for improving the Submittals tool. This tool is very similar to the Reviews tool, with nearly identical core functionality, but the flexibility for project admins is much more limited compared to Reviews. Would it be possible to extend the Submittals functions with the same features as in Reviews? This shouldn’t be too difficult since the functionality already exists in the software. For example, adding the option to choose between calendar and working days, which is currently unavailable in the Submittals tool but available in Reviews. Another issue is that you can’t prepare Submittal templates in the project template, whereas the Reviews tool allows this. Speaking of templates, would it be possible to release API endpoints for both Reviews and Submittals, specifically GET and POST, to enable automatic posting of both tool templates to new projects?   I believe these suggestions would significantly enhance the usability of both tools.   Thanks and see you!  Show More

ACC project templates reside on one hub that can be accessed for project creation from another hub. The same template could be used to create projects on different hubs or different regions.   Currently a project can be created on the hub where the template resides. So, if a firm has multiple hubs, we have to recreate the same template across multiple hubs and multiple regions. There is currently no way to copy an ACC template across hubs or across regions. Creating or modifying templates have to be performed manually across multiple hubs.   The Content Catalog can be accessed from a different hub other than where the project resides - the same function is needed for ACC project templates. Templates live on a single hub. ACC projects could be created on any hub the administrator belongs to. Show More

As multiple ACC hubs can be enabled under a single Autodesk account, it would be more effective for the ACC Library to be managed at a level above each individual hub. For example, if an organisation has three hubs representing different office locations, each currently requires its own ACC Library to be managed independently.   Managing the library above the hub level would allow each office or division within the same organisation to work independently while maintaining company-wide standardisation. It would also help reduce administrative effort. @twellins  Show More

Enabling Account and Project Admins to define what project members can view based on their permissions across ACC tools, would provide greater flexibility in project management. This could be implemented as a temporary visibility feature that allows admins to toggle between different permission assignments based on user, role and company. Show More

Open up the API's for corrections request so we can pull that information into our data warehouse for project team visibility. Due to other issues that I have posted about we do not want project teams in the trade tapp system but this would allow them full visibility of the subs they are tracking.  Show More

We almost only use build. People with a build license will automatically have a Docs license also. Why cant we have a single menu (left pane) with selected options that we want available for our users? Ideally: in a project template let us setup what sections are available, whether they are for docs or build? For Docs-only users that will automatically revert to only the docs-sections to be available but for the Build users that would save them the effort between switching between docs and build for just those few sections that are only availble in docs (like review). Show More