Help shape the future of Box
Welcome to Box Pulse, our product feedback tool powered by UserVoice. Got an idea for how to improve Box? Share it with us and gather support or vote on other people's ideas. Your feedback is essential to informing roadmap decisions and shaping the future of our products. Thanks for joining our community!
See user guide here.
161 results found
-
Increase of the upper limit on the number of metadata templates that can be created and permission management for metadata templates
Currently, our company has a wide variety of unstructured data, and we would like to make use of metadata templates. However, there are significant differences in the templates that each on-site team wants to use. At present, metadata templates can only be created up to 500 per tenant, which leads to competition over templates. We would like to be able to create an almost unlimited number of metadata templates.
In addition, once a metadata template is created, it becomes viewable across the entire tenant, which feels inconsistent with Box’s underlying philosophy of content-level permission management. We would like metadata templates…18 votes -
Metadata attribute update
As the increased use of metadata becomes popular, it would be great to have updates attributes in the metadata templates automatically update in the file requests/ forms or metadata options where they are being used.
Currently, in files requests and forms the metadata templates needs to be manually updated in the designated forms, which can be hard to track.
Request: metadata updates to attributes to be dynamically updated in their embedded/ functionality locations
12 votes -
Automatic Translation of Metadata Template Fields
When companies with international operations use Box, changing the language of Box itself does not translate the fields in metadata templates. Therefore, if there are users who speak multiple languages within the same tenant, it is necessary to prepare separate metadata templates for each language. However, since only up to 500 templates can be created, it is difficult to prepare one for each language. Please implement automatic translation for a single metadata template so that users of other languages can also use the same metadata template.
-in Japanese-
海外展開している企業でBoxを利用する場合、Box自体の言語を変更してもメタデータテンプレートの項目は翻訳されません。そのため、同一のテナントで複数言語ユーザーが存在する場合、言語ごとにメタデータテンプレートを用意する必要がありますが、500個までしか作れないため、言語ごとに用意することが難しいです。一つのメタデータテンプレートを自動翻訳し、他言語のユーザーも同一のメタデータテンプレートが利用できるようにしてください。1 vote -
Automatic Translation of Metadata Based on Language
When companies expanding overseas use Box, if metadata contains text in a specific country’s language, they must search using that same language. While Box’s UI allows users to change the language, and standard searches can find files in other languages using AI Home, metadata is not supported by AI Home’s search functionality, making multilingual searches impossible. We would like to see automatic translation of metadata or support for multilingual searches using AI Home.
-in Japanese-
海外展開している企業でBoxを利用する場合、メタデータで一意の国の言語が使われているときは、同じ言語で検索する必要があります。BoxのUIは言語変更が可能で、通常の検索についてもAI Homeを利用することで別言語のファイル検索が可能ですが、メタデータについてはAI Homeの検索に対応しておらず、多言語での検索ができません。メタデータの自動翻訳、もしくはAI Homeを用いた多言語検索対応ができるようにしてほしいです。1 vote -
Add a "User must pick from the lowest available level" option when adding a Taxonomy to a Metadata Template
The existing options for "What level(s) can users select a value from?" have their use cases, but they do not cover all of the potential applications of the Taxonomy system.
Right now, when I add a taxonomy to a metadata template, the options are "Users must pick from the following level: [level]", and "Users can pick from any level in the list". What I would like to propose is a third option, "User must pick from the lowest available level".
The intent behind this would be to accommodate for Taxonomies where not every item has child items. In much of…
1 vote -
List with optional Freeform
Provide users with the ability to enter free-form text into a LIST/Dropdown selection field when reviewing AI-Extract Metadata and then having that entered Text become part of the drop-down selection. See attached picture from another web-based tool with this functionality where admin can toggle on/off if they want it applied or not.
1 vote -
Allow Metadata Updates While a File Is Being Edited or Locked
Currently, file metadata cannot be updated when the file is being edited or locked by another user.
This behavior interferes with background systems that automatically apply or update metadata in response to events such as webhooks. For example, even when a background process only needs to update metadata and does not modify the file content itself, the metadata update fails if the file is currently locked.
We believe that restricting metadata updates simply because the file content is not writable is undesirable. Metadata updates should be treated independently from modifications to the file content.
Please provide a way to update…
1 vote -
Ability for end users (non admins) to adjust metadata
As Box is evolving more into metadata driven workflows for digital asset library use cases, we need the ability for end users (non admins) to be able to adjust metadata templates specific to their use case or business unit. For example, we'd like to have a champion from Marketing be able to adjust JUST the metadata templates specific to their group, not any metadata templates related to Legal or Sales.
6 votes -
Make folder retention policies non-removable (or always visible) to Editors
Today, Editors can remove the visible retention policy from a file or folder’s details panel, even though the underlying non-modifiable retention policy remains active in the background. This means that after an Editor removes the visible policy, there is no indication in the UI that retention still applies, which makes it appear as though the content is not under retention at all.
This behavior causes confusion for end users and admins, and makes it harder to support clear records management and compliance because enforced retention is not transparently visible in the interface.
Feature request
Please provide one or more of…3 votes -
Enable assignement of taxonomy metadata fields using variables in Add Metadata Outcome
Currently, a taxonomy field in the metadata template used by a form can be completed (that is, the person completing the form can select a value from the taxonomy), but in an Automate workflow the value that is selected cannot be applied to a file using the Add Metadata outcome, because that field type does not allow value assignment via a variable.
The only way to make this work is to use a Dropdown field in the metadata template. Those do allow the use of variables to assign values in the Add Metadata step. BUT, that creates a maintenance nightmare…
1 vote -
We would like metadata to also be stored in the specified Zone.
In Box Zones settings, content can be stored in the specified zone, but metadata is always stored in the United States.
We would like metadata to be stored in the specified zone as well.Box Zonesの設定では、コンテンツは指定したZoneに保存できますが、メタデータは必ず米国に保存されます。
メタデータも指定したZoneへの保存できるようにしたいです。13 votes -
Metadata Save and Cancel options on folders
I'd like to request to include the Save and Cancel option for Metadata on a folder.
Metadata (retention) templates are applied immediately upon selection on a folder. Because the interface does not feature a secondary "Cancel" or "Save" button, the policy takes effect the moment the template is chosen (=added), making any subsequent cancellation irrelevant to the already-applied configuration. This behavior does not occur when adding metadata to individual files.1 vote -
Controlling metadata templates
I would like to be able to determine the scope to which metadata template creators can make their templates public.
1 vote -
Metadata analytics and reporting
Incorporating custom metadata fields, tags, and properties into analysis would provide much richer context and more accurate insights
2 votes -
Expandable metadata description fields
When adding descriptions for metadata fields (for the purposes of prompting the AI for MDE), the input field is too small, and my customer cannot see the prompts to edit in the UI. Please allow those fields to be expandable (up to the max character limit) to improve the UX for my customer.
1 vote -
More granular visibility on Metadata Cascade Policies for folders
Currently, when getting info for folders via API, users are able to see whether a cascading metadata policy is set, but can't see if it is set to override existing values, only apply to new instances, or not overwrite anything. Some customers would like more detail included with whether or not a cascade policy exists and what it's set to
1 vote -
webhook metadata
Include all the metadata key/value pairs in the webhook payload when METADATA_INSTANCE.CREATED event is triggered so clients don't have send an additional GET request to fetch the metadata values.
4 votes -
bulk update metadata
For metadata driven relays, it would useful from the list view to be able to multiselect files within a folder and set the meta value for a particular field for all the selected files.
3 votes -
Bulk Metadata View for File Request Files
We’re using a File Request form with a metadata template that collects applicant and writer info. That metadata is used for renaming applications and triggering other Relay steps.
What’s missing is a way to see all that metadata at once. Something like a folder-level view or export that shows a list of the metadata values ie(ApplicantName, ApplicantEmail, WriterName, WriterEmail). Right now the only option is opening the metadata tab on each file one by one, which doesn’t scale when there are a lot of submissions.
A simple list or export of all metadata in a folder would make managing these…
1 vote -
is there a way to auto populate a metadata attributes such as employee name from a csv list or automatically from the box users?
It would be nice if we could populate or employee name attribute list from either a csv file of usernames or directly from the usernames in the admin console.
3 votes
- Don't see your idea?