Currently, markups in Autodesk Vault are stored as entity attributes linked to the DWF version. These markups are separated from the markups created in the online viewer within Fusion Manage (FM). A valuable enhancement would be the ability for Vault to store markups directly in the Vault database instead of saving them only as image files. This would allow markups created in Vault to become accessible and reusable within Fusion Manage, enabling a common review and collaboration workflow across both systems.   Current Situation Vault markups are stored as entity attributes on DWF versions Fusion Manage online viewer markups are handled separately Vault currently stores markups only as image files No shared markup repository exists between Vault and FM Requested Enhancement Extend the Vault markup functionality so that: Markups are stored directly in the Vault database Markup data can be associated with Vault entities and DWF versions Markups become accessible from both Vault and Fusion Manage Shared collaborative reviews between Vault users and FM users are possible Benefits Unified review workflow across Vault and Fusion Manage Better collaboration between engineering and downstream teams Centralized markup history and traceability Reduced duplication of review comments Improved lifecycle and change management processes Consistent markup visibility independent of client application Use Case Engineering teams review CAD data in Vault, while project or change management teams review the same data in Fusion Manage. Shared markups would allow all stakeholders to work on the same review annotations without maintaining separate comment systems. This would significantly improve connected workflows between Vault and Fusion Manage environments. Show More

It would be helpful if the user received a notification in Inventor indicating that they are not currently working with the latest project file from the Vault. Especially in large environments, you don’t always want to have to notify 300 (or more) users that they need to double-click the project file because a change has been made. Show More

Hi everyone, It would be very helpful to have the option to control the visibility of the Quick Search tool. This is how it looks by default:  Ideally, there should be an option to keep it permanently like this:  The reason is performance: in large vault environments, the default Quick Search can significantly slow down the vault server. In contrast, searching using multiple properties leads to much better performance and a smoother experience.       Hallo zusammen, es wäre sehr hilfreich, die Sichtbarkeit der Quick Search steuern zu können. So sieht sie aktuell standardmäßig aus:  Wünschenswert wäre eine Option, sie dauerhaft so darzustellen:  Der Hintergrund ist die Performance: In großen Vault-Umgebungen kann die standardmäßige Quick Search den Server deutlich verlangsamen. Die Suche über mehrere Eigenschaften hingegen verbessert die Systemleistung spürbar und sorgt für ein flüssigeres Arbeiten. Show More

It would be great if all checked-out files were displayed in Vault Thin Client as they are in Vault Pro. The files should also be crossed out.     Show More

In daily use of Autodesk Vault, it is very common to work across both Project Explorer and Item Master. Currently, users can switch between these environments, but they cannot be open at the same time. This creates a real productivity issue. Every time users switch between environments: searches are reset filters must be re-entered working context is lost workflow is interrupted This happens many times per day in real scenarios, such as searching for an item and checking the related file, comparing file structure and item structure, or navigating revisions and components. Proposal: Allow Project Explorer and Item Master to be opened in separate windows or independent tabs, similar to modern web browsers. Each window should preserve searches and filters, maintain navigation state, and be usable in parallel, including on multiple monitors. Benefits: reduce repetitive operations save time in daily workflows improve workflow continuity allow faster comparison between data increase efficiency for advanced users Note: This is not just a user interface improvement, but a real productivity improvement for daily work. Even a simple solution, such as allowing multiple Vault client windows, would already provide significant benefits.   Thank you for your attention. Show More

In Vault 2025 Thick Client and Thin Client, the integrated Autodesk Viewer shows the “Display Edges” option, but it is disabled or has no effect for Inventor IPT/IAM files. This makes technical review difficult compared with Inventor’s “Shaded with Edges” display. Please enable visible model edges for Inventor files in the Vault integrated viewer, or provide an administrator/user setting to force edges visibility by default. Show More

Dear Autodesk Team, when renaming a top-level or nested assembly, users often need to rename related subassemblies and parts to maintain consistent naming conventions. Automatically including all child components would greatly simplify this process. Description: Currently, when using the Rename Wizard in Autodesk Vault, there is no option to automatically include all child components (subassemblies and parts) of a selected assembly. This means that users must manually locate and add each subassembly and part to the Rename Wizard if they also need to be renamed. This can be very time-consuming and error-prone, especially for large and deeply nested assembly structures. Requested enhancement: Please add an option in the Rename Wizard to automatically include all child components of the selected assembly, similar to how the Copy Design wizard loads the full structure. For example, a checkbox such as: "Include all child components" or "Load full assembly structure" Benefits: Saves significant time when renaming assembly structures Reduces the risk of missing components Improves workflow efficiency and usability Makes the Rename Wizard more consistent with the Copy Design workflow Thank you for considering this enhancement.   https://forums.autodesk.com/t5/vault-forum/rename-nested-assembly-in-autodesk-vault-include-all/m-p/14005759#M52760 Show More

For example, if a job processor machine has trouble obtaining a license, it currently “kills” all tasks in the scheduler for its fellow job processors. Preferred behavior: after, for example, 3 consecutive failed tasks of the same type, the affected job processor should stop processing further tasks. It would also be helpful to send an email notification to the administrator. Show More

Hello.   It would be great to be able to distinguish between standard and weldment assembly and standard and sheet metal part in Vault. Currently there is only iam and ipt, but there is no information about sub-environments. It probably can be done by "user parameter", but it would be better that it is a "System" one. And also this includes different icons of course.     Best regards, Rene Repina Show More

It would be helpful to be able to export comparison bills of materials from Vault while retaining the existing formatting. This includes, among other things, that color-highlighted cells (e.g. blue) keep their highlighting and that struck-through items are displayed accordingly in the export. With the export options currently available—such as copying rows via “Copy & Paste” into Excel or using Vault reports—this is not possible at present. Show More

I believe it would be extremely valuable to have a centralized visualization and management tool for security permissions across all files and folders within a Vault environment. Currently, understanding and managing permissions can be complex—especially for non-expert administrators. There is no native tool (to my knowledge) that provides a global, intuitive overview of permissions or helps identify inconsistencies with the overall security policy of the Vault. Such a tool should provide: A global and hierarchical view of permissions across the entire Vault (files and folders) The ability to easily identify non-compliant or inconsistent permissions compared to defined security policies A clear and graphical representation of inherited vs. explicit permissions Advanced filtering options (by user, group, role, folder, permission type, etc.) A way to quickly audit and troubleshoot access issues The plugin Effective Permissions Viewer available on the Autodesk App Store is a great starting point. It offers a visual and informative interface that makes permission analysis much easier and more accessible. However, it remains limited in scope and lacks native integration and advanced management capabilities. Building on this concept, a native Vault feature could go further by: Allowing bulk editing and deployment of permissions across multiple folders/files Simplifying the creation and assignment of new user groups Providing simulation tools (e.g., "what access would this user/group have?"? Offering policy enforcement mechanisms to automatically detect and correct deviations Enabling reporting/exporting capabilities for audits and compliance tracking This would significantly improve security management, reduce configuration errors, and save a considerable amount of time for administrators. Show More

Sometimes shop users using the thin client try to view a dxf file and when nothing shows up they click on the update visualization button.  Then it just sits in the queue until I go and remove it.  It would be nice if the option just wasn't there to try and update the visualization for files that it can't create a dwf for. Show More

Problem A very common requirement in Vault is to automatically populate revision and approval fields on drawings based on lifecycle state changes (Designer, Checker, Approver, Approval Date, Reason for Issue, etc.). Today, this typically requires: Third‑party Vault extensions, or Custom jobs built on top of the Job Processor The end goal for most users is simple: clean, correct data that can be shown directly in the drawing revision block.   Proposed solution – Property mapping on state change Introduce a built‑in Property Mapping on Lifecycle State Change feature. On each lifecycle transition, administrators can define one or more mapping rules: Source: system property, user‑defined property, or static text Target: any writable property Action: copy value, set static value, or clear value The mappings are executed automatically on state change, using the existing Job Processor. This provides a generic and flexible automation mechanism for setting, transferring, or clearing properties based on lifecycle transitions, without custom API code or third‑party extensions.   Example workflow Typical use cases include populating revision tables, drawing signatures, approval initials, and approval dates based on lifecycle state changes. Work in Progress → For Review Copy Created By → Designer For Review → For Approval Copy Created By → Checked By For Approval → Released Copy Created By → Eng. Approved By Copy Created Date → Eng. Approved Date Set Reason for Issue = "Issued for Construction" Released → Work in Progress Clear approval and revision‑related properties These properties can then be referenced directly in the drawing revision block, which is the primary driver for this feature.   Value Clean, automatic revision and approval data without custom jobs or extensions A reusable automation mechanism for lifecycle-driven metadata Show More

Hello, Automatic flat pattern exports of sheet metal parts to DXF in Vault are a very interesting feature. I would like to add a criterion in their configuration options to select the model state to be used during this export. This criterion would allow choosing the default model state that should be activated for the export; if it is inaccessible, then the "Master" state would be selected instead. This would make it possible to handle, for example, cut and machined parts requiring an allowance for material removal, which may have a model state such as "As-cut part," or cases where the cutting contour is managed within a specific model state. The default parameter for this criterion would be "Master," and the administrator could enter a specific model state that would then take priority. Thanks. Vincent. Show More

We have do export our dwg as an eTransmitt out of AutoCAD at the end f our projects. This are may fils and exports. It wozld be grate, if there is a job of the job-processor that can do this automaticaly. It schuld be possible to config the settings for the eTransmitt. It have to be possible to define the settings specicicaly for diffrent projects, may be by using the category of the file. Show More

When I do a search in Vault sometime I get a result of hundreds or thousands files, I then have to keep hitting the More button I until Vault shows me all the files it found.   What I would love is a Show All button.  When I click on the this button, Vault will then display all the files it found.   I know that this can take some time for it to finish but it's better than me sitting there hit More over and over again. Show More

After Item is created, if I change Part Number in the .ipt or .iam,  Item won't be updated correctly. We need to break link before update. See video Show More

Please allow the ability to set defined users able to run the Job Processor utility so just any account with Vault access can't run it. We've ran into an issue twice now where a random user has launched the Vault Job Processor on their machine (on accident and unknowingly) and it is picking up jobs without the correct permissions and configuration. It would be nice to have the option to limit the Job Processor role to a specific user(s) to prevent a job being processed on the wrong machine/setup. Thanks! Show More

The Inventor function « Map folders » allow to map Vault folders in the Designs.ipj file. An « Edit » button allows to browse a new folder. But there is no solution to delete a folder mapping. Please add a « Delete » button to delete a mapping. Please check the attached picture. Folder_Mapping_Delete.png Can be useful for example to delete the “Design Data” and “Tempalte” mapping because we stop to use Inventor configuration file inside Vault. Thank you in advance. Show More