Link document class across multiple libraries
Issue: Currently, a document class is created and configured per library. A document class named "Audit Report" may be required in multiple libraries.
Solution: I'm proposing to have a setting that allows for document classes to be linked across multiple libraries. A possible solution would be to pick a document class from a list of preconfigured document classes in the library administration interface (similar to how the "Reference Catalog" behaves with metadata properties).
This would ensure all document classes with the same name are central and standard throughout a domain. The document class would share the same properties, templates & customization but differ in terms of security & permissions.