Templates - Restrict Templates to Specific Users/Groups and/or Folder Structures
Metadata templates are currently global across an entire EID. This does not scale well for large organizations with 50,000, 100,000 or more than 200,000 users.
This request is to add 'scope' parameters to Metadata Templates such that a specific template can be restricted to...
1. A specific set of users
2. A specific set of Groups
3. A specific Folder structure
Brad Monroe
shared this idea
This is still on our roadmap and is under development.
-
G George
commented
Is there any update on this as to where it is in the roadmap. If BOX is to compete in the DAM arena for media and entertainment then this is crucial.
I would love to see this sooner rather than later. -
matsumoto
commented
Currently, when a metadata template is created, it is published within the tenant.
Thus, all metadata is desplayed , make it difficult use when setting metadata. Also, there is a possibility that metadata will be setting to content that shloud not be.So, when creating a metadata template, we would like to make metadata template only be used under a specific folder by allowing the user to select the folder to be used.
(in Japanese)
【メタデータテンプレートを設定する時、フォルダを指定し、そのフォルダ配下でのみで使用したい】現在メタデータテンプレートを作成すると全体に公開されてしまうため、必要なコンテンツ以外にメタデータテンプレートが付与されてしまう可能性があります。
また、たくさんのテンプレートが見えると非常に使いにくいです。メタデータテンプレートの設定をする時、ユーザーが利用できるフォルダを指定し、特定のフォルダ配下のみで利用できるようにしてほしいです。
-
AdminApurva Parikh
(Admin, Box)
commented
Comment from USAA:
We are working on the event-based retention policy in Box and find it’s challenging for users to be exposed to the large number of templates that are created for event/metadata-based retention purpose. Ideally a template would be scoped – e.g, visible to certain teams, or under certain folders.One idea proposed is to leverage the "ownership" model with templates. This would mean any template could be assigned access via a folder owner. We would typically do this with service account owners and not actual users with a few exceptions. This does mean that metadata templates would apply in a cascading fashion, but at least only where assigned.
-
Anonymous
commented
Hello. The use case would be having granular controls over metadata templates for specific departments/groups in Box. For example, the marketing team would have their own unique set of metadata templates to access and the legal team would have their own. This would eliminate any user confusion on all the template across the enterprise they would have access to and choosing the wrong template. Having the granular controls would make the process more efficient and result in a more refined way of searching
-
James Hao
commented
I believe that this feature would be very important. There is currently no granular permissions for metadata. It is either on or off, for any folders and all users (internal and external collaborators).
-
AdminMilo Parsons
(Admin, Box)
commented
Allow for group permissions to be placed on metadata templates so that only those part of that group can add and edit the metadata template on content e.g. only the marketing group can use the marketing campaign taxonomy