Skip to content

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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

14 results found

  1. Relay Reports

    Create a Report so I can export the task history of a Relay or selection of relays across a timeframe for all or selected users

    32 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Workflow  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Add "Updated/Changed" File Event as a Trigger

    Add "Updated/Changed" File Event as a Trigger.

    Triggering a Relay on a specific file when it has been updated directly or updated with an upload, maintaining file history.

    The current workaround is to create a "New upload" Trigger, then the file needs to be Deleted and create/uploaded from new, thus requiring 2 steps and losing file history.

    25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Workflow  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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.

    誤操作により、本来権限を付与されるべきではないユーザーがコラボレートされてしまう可能性があるため、
    チェックボックスのチェックを任意で外せるようにしてほしい。

    26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Workflow  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. The option to cascade Relay triggers to subfolders for all triggers

    Box needs to add the cascade option to all Relay triggers to catch activity in underlying subfolders. The legacy automations feature that Box had did this by default. Now, the alternative is having to create several relay workflows that is too cumbersome to manage and doesn't scale.

    35 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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.

    30 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Workflow  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Create a Box group/alias or ability to select a different name to replace the workflow owner’s name.

    I’ve created several Relay workflows across the business and the issue I found is that people are reaching out to me because my name is tied to a task that is assigned to them. Often times, I do not have any context to the workflow so it results in me having to reach out to the person who started/uploaded the document. We want to avoid approvers having to reach out to the workflow owner vs. the actual owner of the program. This process would not be sustainable if it were rolled out to a larger company.

    Currently Example: Hayley creates…

    111 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Workflow  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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…

    39 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Workflow  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Workflow  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Workflow  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Admin Dashboard with visualizations of workflow stats

    Looking for additional visual methods for a project manager or process owner to access open Relay workflows/action items

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Workflow  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base