Vault publishing guidelines

When you register as a publisher, you'll see the complete requirements in the Publisher Agreement. This guide summarizes the key points — the agreement takes precedence if anything differs.

When you submit your app, the form collects everything needed for your listing — including content for the quick-start page that's included with downloads and viewable online.

Compatibility

Your product must be relevant to (and usable with) Autodesk® Vault® 2026 and must run on any Windows operating system supported by Vault 2026. You may also indicate compatibility with Vault 2025 | 2024 | 2023 | 2022 | 2021.

Your product must work with any higher tiered version of the Vault product. For example, if your application works with Vault Basic it must also work with Vault Workgroup and Vault Professional.

All applications should interact with Vault only through the public API (as defined by the Vault SDK). There should be no direct interaction with server data such as the database tables or file store folders.

User privileges

The default user privilege for the Store apps is Windows 10/11 Admin User. The installer should have elevated user privileges.

Product stability

Your product should be stable and not behave or alter the behavior of Vault in a way that we deem unsuitable, for example, blocking standard functionality, adding functionality already existing in a higher tier of Vault, blocking the functionality of another plug-in, causing data loss, etc.

Applications that check out and check in files should be preserving meta-data in the case of Autodesk file types.

All applications should work in and be compatible with a multisite or replicated environment.

HTML help page

When you submit your app, the documentation form generates a help page that's included with your download. Make sure your instructions are clear and actionable — users should be able to get started quickly. You can link to additional resources hosted on your website.

Ready to run

Your app must work immediately after installation — no manual file copying, registration, or settings changes required. The autoloader mechanism described below can help you achieve this.

If your app uses licensing:

• Activate automatically (e.g., online activation), or
• Include a fully functional trial period long enough to deliver activation to the customer.

Questions? Email appsubmissions@autodesk.com for support.

For more resources, visit the API documentation and the Developer Community Blog.