cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Allow to PDF publish to inherit security

Allow to PDF publish to inherit security

Great that pdf publishing is implemented. Also great that it allows to inherit revision and properties from the parent (native) document. This helps users without CAD to view documents through e.g. Thin Client. Security, on the other hand, is missing because all pdf's publish to the same category despite their parents category.

 

Dwf's inherit security from their parent because they are only available via a link from the parent (if you have access to the parent you have access to the dwf, if you don't you cannot access the dwf through the Thin Client interface)

 

It would help a lot if the published pdf inherits security from the parent (category / lifecycle).

 

E.g. a plant owner/operator manages documents from their buildings and installations in Vault. Some of these documents are available to a small user group like documents from the CCTV or Access Control system. A specific category allows you to secure access for native documents, but not for their published pdf's.

 

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea