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.
11 results found
-
Ability to include the name of the triggered file in the subject line when sending Relay notifications
We would like to be able to include the name of the triggered file in the subject line when sending Relay notifications.
We want to be able to easily check which file the notification is for when the user who received the notification receives the notification email.
When a user receives a notification email, I want to be able to easily check which file it is for.
(In Japanese)
通知の相手に割り当てられたユーザーへの通知の際にファイル名を含めた通知を行いたい。
通知を受け取ったユーザーが通知メールを受け取っても、どのファイルに対する通知なのかを
簡単に確認できるようにしたい。22 votesWe are conducting user feedback sessions to gather more information
-
Relay：Enable/disable the "Invite assignees as Viewers/Editors" option
A new feature has been added to Relay called "Invite assignees as Virwers/Editors".
Perhaps, it is possible that, due to a mistake, users who should not be collaborating are automatically collaborated with.
However, in the current specification, the checkbox for this feature cannot be changed from enabled.We would like the checkbox to be able to be unchecked optionally.
誤操作により、本来権限を付与されるべきではないユーザーがコラボレートされてしまう可能性があるため、
チェックボックスのチェックを任意で外せるようにしてほしい。29 votesWe are conducting user feedback sessions to gather more information
-
Allow groups to be added as collaborators in Relay “Add Collaborator” outcome
Would be great to be able to add a group of collaborators “Add Collaborator” outcome. Right now only single users are accepted as input.
35 votesWe are conducting user feedback sessions to gather more information
-
API for "CRUD" for Box Relay and Box Relay Lite
We have created over a hundred of Relay workflows and have currently faced a difficulty in adjusting all rules when our orgnization is changed. We would like to have a set of APIs for Relay for creation, reference, update and delete operations (so called CRUD).
Also we would like to have an way to update folder ID(s) on existing workflows. It would help so much especially when annual org change happens.
19 votes -
File request - Block upload of domains not on enterprise allowlisted domains
For File Request where Enterprise requires user to login prior to submission, would like an additional security check for Enterprises that only allow for external collaboration from allowed domains as listed in the Enterprise console. If the domain is on the list then allow for file request upload, if domain is not on the allowlisted domains, block upload.
25 votes -
Support multi-file for rejected task trigger in Relay
Suppose you like to assign an approval task to a person with multiple files and when the task is rejected, you like to move the package of those “rejected” files to a different folder("Rejected folder) instead of having them sat in the triggered folder.
For a single file, you can create the following workflow containing 2 flows and it works perfect as expected, however it doesn't work for multi-files...
Flow 1: Trigger Manual start-> Outcome: Assign task -> When rejected, the flow is end
Flow 2: Trigger Task -> Outcome: when the task is rejected, move the file to “Rejected…40 votesWe are conducting user feedback sessions to gather more information
-
Automatic email response for file request submitter
Would like a feature whereby the person submitting files using Box File Request receives an automatic confirmation email with a customizable message. For example, after the submitter uploads files using the File Request web widget, that person gets a email to the effect of, "Thank you for contacting us. A team member will review your submittal and follow up within 24 hours." The person would be required to provide an email address but not required to have a Box account. Many of our external customers send us application materials using File Request, and then they contact us separately wanting to…
45 votes -
Allow the Admin to Set File Request requirements and default settings
Allow admins to require all File Requests globally to have certain fields (like email address or a pre-populated description Box with a legal disclaimer) or settings
17 votes -
Report on who has Relay enabled
Ability to report on who has Relay enabled in an enterprise account. Via "Export users" would be nice, but not even Box's own reporting team can produce this data right now which is unfathomable.
5 votesWe are conducting user feedback sessions to gather more information
-
Template Version History
We would like to have a history of changes made to templates so if they modify one they can revert back if needed or have a record of who changed what/when - one use case is for compliance templates they need insight in to who created/when but also iterations of the template
3 votes -
Ability to view template Version History
We would like to have a history of changes made to templates. If we modify one, we can revert back if needed or have a record of who changed what/when. For Compliance templates, we need insight into who created/when but also iterations of the template.
0 votes
- Don't see your idea?