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.
34 results found
-
File Request expiration
Due to security concerns, we have implemented an enterprise setting for shared link expiration. We would like to be able to do this with File Request links as well, but that is not a configuration option available. Would it be possible to add this functionality?
4 votes -
Changes to workflow builder functionality
Create changes to workflow builder functionality:
1. Allow folder Editors to be able to build workflows (we have very few co-admins)
2. Allow the workflow builder to specify who is assigning the task (or make it generic.) Just because Bob builds the workflow doesn't mean his name should be on the assigning task.25 votesThanks for your feedback!
1. Editors are now able to build workflows (delivered in Q1)
2. We’ll certainly investigate the task assignee feedback in future feature updates as well, thanks! -
Relay: Copy or move the contents of a folder rather than the folder itself
Currently Relay can copy a file or a folder, but not all the contents of a folder to a location. This would be really useful for content propagation, where the use case would be that every time a folder is created copy the content of a template to it.
8 votesThis is possible today with the “copy folder” outcome.
-
name folder based on data created
When a new folder is created through Relay, have various options to name the file beyond a default name field, such as data created as an insert field variable.
3 votes -
I want multiple approvers on every workflow.
We have external approvers and one of them should be able to advance this workflow.
3 votes -
Add naming flow when relay creates a folder or file
When relay creates a folder or file, we want relay to guide user to name the folder or file as a flow.
1 voteYou could solve this today by assigning a task to the user to name the file.
-
Add and more events into a same flow in relay
When You build a flow in relay, You don't have the possibility to add another event into this same flow as a result. This might help if You need to repeat a part of the flow (similar as a loop).
3 votesThis is a feature that is available for paid Relay customers
-
possibility to call another relay automation
I made a scenario with relay and I would like to use it into another instead of creating again and again same flows. So it would be nice to get the possibility to combine different scenarios as sub-scenarios (like procedures in a program).
2 votesAs part of paid Relay, you can set various metadata values to trigger different aspects of the process.
-
Ability to mirror documents in other root folders
Our organization utilizes the collaboration with external users to give them access to view one specific folder relative to their client account. We do not want these users to have access to our main folder that houses the original documents for their client account, but rather only this one specific folder that has a copy of selected documents relative to their positions on the Board. Right now, we have to manually upload or delete new documents to both folders. If there is a change to our original document, we have to manually upload the new version to the copy folder…
1 voteHello, if we understand your request correctly, you could use the bookmark feature to bookmark a link to specific files so the Board will always be routed to the up-to-date version of the original document but not be able to view the rest of the items in the main folder.
-
Add watermarks via Relay
Allow users to add watermarks to files as part of a Relay process.
2 votes -
Automations: Enable an ‘and/or’ feature
Enable an ‘and/or’ feature for Automations that allows task to be approved by one assignee in order to move forward in the workflow
3 votes -
show automation creator as the sender of automation task assignment email
Currently, automation task email notifications show the sender as the primary email regardless of who created the automation
In a large company, users might not even know who the admin is and discard the emails as spam or unnecessary.
4 votesAvailable in Relay
-
Give users access to Automations without becoming a co-admin
Certain communications do not need to go to Automations creators. Rather, they are truly meant for co-admins. Additional granularity would help reduce noise.
2 votesCan enable user with Relay without them being a co-admin
-
2 votes
Available in Relay
-
Workflow phases for easier understanding of progress
We have a workflow that could be over 25 steps in total. These steps are separated, in their original design, into phases such as Preparation > Briefing > Development > Sign-off > Release. Currently, it's impossible for users to see which stage they are in or which stages have been completed, as they are not defined. A user would have to know the number of steps in each phase to understand this currently. Phasing is a basic feature included in most workflow systems.
2 votes -
Export audit report of completed workflows
The customer has a requirement to be able to export information out of Relay in report of Excel format - ex) export a report of the steps completed in a workflow with due dates, dates of completion, by whom etc so they can present this information to clients or have it for internal audits. the workflow dashboard view is a helpful visual but they don't want to click in to each workflow to visually consume that information each time and be able to send it to other folks outside of Relay
10 votesAvailable in Relay
-
1 vote
-
Admin settings for who can create templates
We want to provide a set of approved templates for policy approvals that users can launch, but don't want them to be able to create their own 'unapproved' templates.
1 voteAvailable in Relay
-
Nested or linked workflows in Relay
I want to be able to nest workflows both for organization purposes and to have a record of all workflows that pertain to a certain project, client, etc. This could be a tag of attribute added to workflows to link them together or an ability to have a set of workflows that are triggered automatically in a certain order so they don't exist completely separate.
2 votesAvailable in Relay
-
3 votes
- Don't see your idea?