topic Block Vault Item Properties for particular user groups using API in Vault Customization Forum

Block Vault Item Properties for particular user groups using API

JRajendran4 — Thu, 08 Jan 2026 12:09:06 GMT

How can item properties be programmatically restricted or blocked for specific user groups using the Vault API? Specifically, how can the Vault API be used to control visibility or edit access to selected Item properties based on user group or role, and what Vault security configurations, property definitions, or permission models (e.g., roles, categories, lifecycle states) are involved to enforce these restrictions?

Re: Block Vault Item Properties for particular user groups using API

Markus.Koechl — Thu, 08 Jan 2026 12:56:43 GMT

You cannot restrict individual properties in Vault. The access control (read, modify, delete, download) applies to an entity and all its properties. Which properties are assigned to an entity is driven by the category (or manually). A category assigns a lifecycle definition and a revision scheme. Access control may vary by lifecycle state, but as noted earlier, if an entity is accessible with modify permissions, all properties are editable (unless they are read-only in file properties). Review the Help documentation for general insights on users, user groups, and roles: https://help.autodesk.com/view/VAULT/2026/ENU/?guid=GUID-428B79D5-7F4B-4182-932A-D52D61BD962D and its chapters, e.g., Roles and Permissions.
I hope this helps.

Re: Block Vault Item Properties for particular user groups using API

JRajendran4 — Thu, 08 Jan 2026 13:17:57 GMT

could you please confirm if there are any recommended workarounds or best practices—such as using multiple categories, lifecycle state transitions, or UI-level customizations (e.g., Vault Client extensions)—to effectively limit user interaction with certain properties?

Re: Block Vault Item Properties for particular user groups using API

Markus.Koechl — Thu, 08 Jan 2026 16:32:25 GMT

I am not aware of any best practice to limit user interactions with user defined propertes (UDP), as it is not a target of the architecture of it.
There is another layer of storing custom data, the EntAttr class; see SDK help documentation:

EntAttr is accessible through API only; so, you can implement all the logic of restrictions etc., but you also must implement your custom UI to display or edit these. DetailPanes, or dockable panes (such as the Properties pane), are the default UI extension to be linked to Items.