International collaboration involves localized clients and multiple client locale settings. Date/Time and number formats may result in misinterpretation, e.g., February 1st 2026 could be displayed as 01/02/2026, 02/01/2026, or 2026/02/01. A hint about the locale behind the values displayed by the Vault server might help avoid uncertainty. What if the Server Address in the Vault Client status bar displayed Date/Time: MM/DD/YYYY and Number: 1.234,56 as a tooltip?  Show More

Standardize Log In/Sign In between Vault Thick Client and Vault Thin Client.  Or allow Admin to configure Sign In page for users.  Confusion with users set up with active Windows Account try to enter credentials and are denied.    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

Hello, It would be extremely helpful for our customers if there were a property in Vault that describes the user who made the last status change. In addition, a property that records the date and time of the last status change would also be helpful. This would save a lot of additional programming and add-ins. Thank you!   Hallo, für unsere Kunden wäre es absolut hilfreich, wenn es eine Eigenschaft in Vault gäbe, die den User des letzten Statuswechsel beschreibt. Zusätzlich wäre eine Eigenschaft hilfreich, die das Datum und Uhrzeit des letzten Statuswechsel schreibt. Das würde viele zusätzliche Programmierung und AddIns sparen. Danke! 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

Vault Server currently requires SQL Authentication during installation and configuration.  The installer only accepts SQL-authenticated logins and does not allow the use of Windows/Active Directory accounts.    We would like to see full support for Windows/AD authentication for the SQL connection used by Vault during: Installation Configuration Vault creation/administration tasks Since Vault does not support Windows/AD, we are forced to request internal security exceptions to enable SQL Authentication solely for Vault deployment and maintenance.    Adding this support would align Vault with modern enterprise security standards, eliminate the need for SQL Authentication in restricted environments and reduce the need for security exceptions. Show More

The number of lines in the criteria list is only 3, I think it should be growing as you add more criteria's for easier overview. Or at least there should be an resizing possibility.     Interestingly, it seems like this was NOT the case some years ago, judging by this old screenshot  I found: (screenshot source: https://forums.autodesk.com/t5/vault-forum/saved-search/m-p/5495501/highlight/true#M44735 )   And while you're at it you could also fix that magnifying glass icon that looks horrible in dark-mode. 😄     Show More

I'd like to disable a specific Vault command in a menu in Inventor Professional 2026. How to reach the menu: load a file in Inventor, go to Vault tab → Show Details → select a tab with a file list, such as "Uses" → right‑click file. Here I want to disable the "Assign/Update Item" context‑menu command. The reason is that the user doesn't accidentally run the Autodesk out-of-the-box command, and thus break the business process and/or the CAD structure metadata. We have our own custom Assign/Update Item commands. Along with disabling UI access, disabling should also prevent any access to it via APIs. Show More

Idea / Request Many customers implement an Item workflow in Autodesk Vault. In these environments, designers often create additional drawing files that reference the same model—e.g., drawings created purely for views, layouts, simplified presentations, manufacturing variants, or internal documentation. Today, when a model is assigned to an Item, Vault attaches all referenced drawings automatically (as intended from a dependency perspective). However, this behavior also attaches “view drawings” and other non-master drawings, which can create noise and administrative overhead. Problem If a model is referenced by multiple drawings (including drawings created only for views), all those drawings are attached/listed under the Item. This becomes a major cleanup task for users, especially in mature Vault environments with many historical drawings and view-based drawings. In most cases, the user wants exactly one drawing to be considered the “main” (master) drawing for the part/assembly, and the other drawings should not drive compliance checks, “up-to-date” validation, or downstream jobs. Impact Excessive manual cleanup and confusion for end users Harder to maintain a clean “source of truth” on the Item level Increased risk of running exports/jobs (PDF/DWF/DXF/STEP, etc.) on the wrong or irrelevant drawing Slower adoption and weaker trust in the Item workflow due to cluttered associations Proposed Feature Introduce a drawing classification concept for Item-associated drawings, such as: Primary Drawing: The main/master drawing for the Item (user-selectable) Secondary Drawing: Additional drawings referencing the model (views, layouts, variants, legacy, etc.) Expected Behavior When assigning a model to an Item, Vault can still detect and list all referencing drawings, but allow marking one as Primary. Users (with permission) can change which drawing is Primary. Provide administrative options (ideal for system architects) to: Ignore Secondary drawings when validating “up-to-date / compliant / latest version” rules Exclude Secondary drawings from Job Processor tasks (or allow job rules that target Primary only) Clearly identify Primary vs Secondary in the UI and APIs (filters, columns, icons) Benefits Significantly reduces Item cleanup effort Improves clarity: one Item → one primary drawing (when desired) Prevents incorrect exports/jobs and improves automation reliability Better user experience and stronger adoption of Item Master workflows   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

Users want the same or similar functionalities in the thin client user interface as we have in the Vault (fat) client. For example, the slider function when columns become wider or the number of columns increases. Currently, users always have to drag the column widths to get a correct display. In fact, it's not even possible to meaningfully display the required column content in the thin client. See also Support Case No. 25383802 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

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

We would like to display the folder links in the Copy Design as they do in DataStandard. When selecting the "Copy to" function, we would like to access the folders in the "My Links" list. ------------------------------------------------------------------------------------------------- Wir möchten gerne im Copy Design die Ordner- Verknüpfungen wie im DataStandard angezeigt bekommen. Wenn man die Funktion "Kopieren in" auswählt, dann würden wir gerne die Ordner in den "Eigenen Verknüpfungen" zugreifen. 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

Hello.   If you could please add a way to edit File Names & File Properties at the same time, it would be a huge efficiency gain and help with preservation of information. This would also help with encouraging file migration for users switching from a Windows Explorer environment to Vault or from migration of alternate competitor programs.   I think this could be achieved in  2 ways: 1) Allow changing of file name in "Property Edits". The area for editing the file name is currently greyed out and locked.     2)    a: Allow rename, copy, and paste in the Rename Wizard.        b: Allow descriptions/fields to be COPIED and then pasted into the file name rename space. I believe this would be the least             effective, but easiest way to allow copying of data between columns to the file name.   Let me know if you have any questions or other considerations. 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

The current LowPriority mode, defined in web.config on ADMS servers, needs more flexibility. (Autodesk docu)   At the moment it is only possible to define a start and end time for every day. It would be nice to define times for each day separately. For example on the weekend it needs no low priority, servers can run with full power.   In our case we have only one DB, subribers are AVFS servers and its a global system, so we have only a slot for 3 hours daily to run not with low priority and on the weekend sometimes we do changes which should be done then with full power.   Thank you Show More

Select the model in the Forge Viewer (Vault) and right-click to view the document or article.   Im Forge Viewer (Vault) Modell auswählen und mit der rechten Maustaste kann dann das Dokument oder Artikel aufgerufen werden. Show More