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.
66 results found
-
Enable True/False Metadata Mapping for Checkboxes and Radio Buttons in Box Forms
Description:
Today in Box Forms, checkbox and radio button inputs are not natively mapped to Boolean metadata fields (true/false or yes/no), which limits the ability to trigger workflows or create metadata-driven views based on user responses.Feature Request:
Allow checkboxes and radio buttons in Box Forms to map directly to Boolean metadata fields:If a checkbox is checked, metadata should reflect “true”; if unchecked, “false.”
For yes/no radio button questions, allow mapping directly to true/false metadata fields.
Impact & Value:
Streamlines workflow automation with Box Relay (e.g., trigger based on form input).
Enables metadata-driven views (e.g., show only records where…
52 votes -
Disposition Report should be able to show files that were deleted in the past
It's important for GxP compliance and ease of auditing to know what files were disposed of in the past, or during a specific period, like in the last 30 days, last 6 months, etc.
Disposition report should be able to show previous deletions, not just upcoming deletions, and admins should be able to filter by retention policy, and date.
31 votes -
form submission export
Box forms submissions should be available via export/report to show each submission and it's form responses, as well as info about the submission (who was it by, when, etc.). This would help with tracking specific forms and reflect functionality with similar products.
14 votes -
Hubs permission model should be more granular
Currently in the Box Hubs Beta, all collaborators invited into a Hub receive the "Viewer" permission on files and folders linked in the Hub. This does not allow for Hub content to be view-only and block downloading of content. Alternative methods of managing this such as rolling out classification policies would not be scalable as Hubs usage grows. It would be great if Hubs collaboration could be more granular and there was an ability to invite users or groups into a Hub with other permissions such as "Previewer" so they are more restricted on what they can do after accessing…
121 votesHello! Changing status on this feature as we have it in our roadmap but we plan to make it in 2-3 quarters. We will keep you updated.
-
Box Hubs Inherited Permissions
The ability to set up a hub that inherits the permissions of the folders/files added. When creating a Hub to have the ability to decide (using a toggle) if content in the Hub should inherit existing permissions or have new permissions granted.
84 votesWe are researching into this feature, thank you!
-
We would like to see Box Hubs have a separate shared link permission setting
Currently, Hub shared links can be allowed from “Enterprise Setting” > “Content & Sharing”, but with the current settings, if Hub shared links are disabled, general folder and file shared links will also be restricted, which is very inconvenient.
Therefore, please consider making the shared link setting of the Hub independent, and allow shared links to be allowed for each individual Hub.【日本語】
現在Hubの共有リンクは、「管理コンソール」＞「コンテンツと共有」から許可できますが、現在の設定値ではHubの共有リンクを禁止すると、通常のフォルダとファイルの共有リンクにも制限がかかってしまい非常に不便です。
そのためHubの共有リンク設定を独立させ、Hub個別で共有リンクの許可を行えるよう検討をお願いします。10 votesThis suggestion is under consideration by the Product Team for future development, however, it is not on our roadmap. Please share additional feedback and use cases to help us understand the importance of this release.
-
Editing Box Hubs: Adding a description to a file or folder
I'd like to be able to add a short description to each file and folder I add to the Hub.
For example, a description is added just below the file or folder icon, or a speech bubble appears when you hover the cursor over the file or folder icon.19 votesThis suggestion is under consideration by the Product Team for future development, however, it is not on our roadmap. Please share additional feedback and use cases to help us understand the importance of this release.
-
Hide contributors on Box Hubs
Customers need the ability to hide who their published Hubs are shared with. They are sharing information with multiple customers who may be competitors of one another, and want to prevent them from seeing who else is accessing the information.
13 votesPreviewer role is under consideration but still not defined on our roadmap. Please share additional feedback and use cases to help us understand the importance of this release.
-
Radio button and Dropdown for Template Tags
We need radio button for Box Sign template tags. We use checkbox for required field instead. When signer forget to check, we need to send another request again.
4 votes -
Checklist on Box Hubs
Having a checklist or tasklist would be really helpful, that way if we had a hub for a project, then you could see the list on the side and know the status of the job.
6 votes -
Dynamically name signed documents based on metadata: signer's full name, company, email and others
When there are documents in the same folder or templates that are repeatably signed with the same name (Ready Sign Link, Batch Send), Box Sign adds a number and () to the filename to note the different/unique files.
There needs to be a better way to name the files - perhaps using metadata or using the unique id of the sign request. And then all files - signed docs and signed log would be renamed with the same name. Otherwise it's very hard to tell files apart when they all have the same name with just a number and ()…
136 votes -
Allow us to put some sort of "Official" Badge on Hubs
Admins should be able to mark official company Hubs to distinguish them from Hubs that organically appear due to team needs. While the latter is great, it would be nice to be able to pin/mark Leadership or HR hubs, for example, to the top of the gallery.
5 votesThis suggestion is under consideration by the Product Team for future development, however, it is not on our roadmap yet. Please share additional feedback and use cases to help us understand the importance of this release.
-
Worflow Starter should be the assigner of tasks instead of the creator/owner of Relay Workflow.
A relay workflow is created by one owner but used by several people. Since all the tasks are assigned by the workflow owner rather than the workflow starter, its confusing for assignees. E-mail and task notifications should show the workflow starter's name instead of the owner of workflow.
34 votes -
Save Microsoft Teams Recordings to Box
When recording a call/meeting in Microsoft Teams, it defaults to using OneDrive as it's default storage. Currently the process of saving a recording is a manual process of downloading the recording, and uploading to Box. I'd like an option to default recording data to Box instead.
29 votes -
External collaboration Allow list per group
We would like to limit the external collaboration to allowed domains for a specific group not the entire tenant.
This is useful when the subsidiary company, especially a financial company, can have a limited external collaboration for security reason.106 votes -
Creating a sign template - Specify a location for saving requests in a folder different from where the template is saved
When creating a sign template, I want to specify a location for saving requests in a folder different from where the template is saved.
Currently, when a request save location is specified in a template, the template is also saved in the specified request save location.
If I move the template file to another folder, the request save location set in the template will also change to the destination folder.
I don't want to re-specify a different folder to save the request each time I create a sign request from a template.
サインテンプレート作成時テンプレートの保存場所とは別のフォルダにリクエストの保存場所を指定したい。
現在、テンプレートでリクエストの保存場所を指定すると、テンプレートも指定したリクエストの保存場所に保存されます。
テンプレートのファイルを別のフォルダに移動するとテンプレート内に設定したリクエストの保存場所も移動先のフォルダに変わってしまう。
テンプレートからサインリクエストを作成するたびにリクエストの保存場所を別のフォルダに指定しなおすのは避けたい。
39 votes -
Fields filled out become metadata
Box Sign - Fields filled out become metadata
94 votes -
Box Sign: Document ID on the header/footer of the document
We would like to add the Document ID number on the header or footer of the documents when we finished signing with Box Sign. We understand that the hard copy is not required as long as the sign is done with Box Sign. But, if we print out the signed document, we can not see any evidence that the signed page is related to the other pages. In the DocuSign, I can see such function.
5 votes -
Ability to specify the destination folder for periodic output of Box reports
We would like to be able to output Box reports periodically by specifying a folder.
Currently, it is possible to output reports on a regular basis, but when providing them to users, it is necessary to manually move the output results, which takes a lot of man-hours.
We would like to be able to fully automate this process, so we are making this request.■日本語
Boxレポートの定期出力をフォルダ指定で出力できるようにしてほしい。
現在は、レポートを定期出力することは可能ですが、ユーザーに提供する場合は手動で出力結果を移動する必要があるため工数がかかってしまいます。
完全自動化できるようにしたいため、リクエストします。57 votes -
Combine Executed Signed Docs and Signature Log
Currently, when you send a document to be signed, the signed executed document and signature log are saved as separate files. It would be nice if the signed doc and signature log were one document and saved as an updated version of the original document. Currently, it turns 1 document into 3 documents, and clutters up the folders.
152 votesWe’re gathering feedback to better understand how merging signed documents and signature logs into a single file could improve your workflow.
Could you share your thoughts on the following?
- Would you expect all completed files, including attachments and the signature log, to be combined into a single PDF?
- Would you need only to merge signed files but not attachments nor signing log?
- What challenges have you faced with having them as separate files?
- How would merging the files improve your process?
Your input will be really helpful as we work on this feature. Thank you.
Best,
Box Product
- Don't see your idea?