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

388 results found

  1. When setting up a BoxRelay workflow, I want to extract only users who have not approved and create approval tasks

    About BoxRelay workflow creation.
    When set up with the following conditions
    Action: Assign task
    Type of task to assign: Approval Task
    Task Details (Person in Charge): Check “This task will be considered complete if one of the persons in charge executes the task.

    We want to be able to extract only the users who did not approve the above settings and set them as the person in charge of approving the next approval task.

    1 vote

    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)
  2. Request Signature outcome should have Form Submitter variable

    When creating a workflow like the one in the following article, the Request Signature outcome cannot use the form submitter as a signer

    https://support.box.com/hc/en-us/articles/38351786879123-Generating-Documents-with-Box-Doc-Gen-and-Box-Relay

    Some of our workflows start with a form, use Box Doc Gen to generate a document, which then needs to be signed by the original form submitter. While the Request Signature step can access form variables, it notably does not have access to the Form Submitter.

    It would be great if this was exposed as a variable so that the sign request could have the submitter as a signer.

    Our current workaround is to add a…

    1 vote

    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)
  3. Request Signature outcome should have Form Submitter variable

    When creating a workflow like the one in the following article, the Request Signature outcome cannot use the form submitter as a signer

    https://support.box.com/hc/en-us/articles/38351786879123-Generating-Documents-with-Box-Doc-Gen-and-Box-Relay

    Some of our workflows start with a form, use Box Doc Gen to generate a document, which then needs to be signed by the original form submitter. While the Request Signature step can access form variables, it notably does not have access to the Form Submitter.

    It would be great if this was exposed as a variable so that the sign request could have the submitter as a signer.

    Our current workaround is to add a…

    1 vote

    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)
  4. Box Relay Send Notification Outcome Tied to a File

    The current "Send Notification" outcome is only capable of sending general notification according to the message set at Box Relay. Can we also tie it with a file similar to the "Assign Task" outcome? Thank you.

    1 vote

    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. 2 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)
  6. Dynamic File Paths for Relay

    I would like there to be an option to include the metadata assigned to a document in the path in a file action for Relay

    1 vote

    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)
  7. We want to use "YYYY MM DD" format for Box Relay date variables

    When entering dates as variables in Box Relay, it is inconvenient that the only formats available are "MM YYYY" or "MM DD YYYY".
    We would like to be able to enter the date in the "YYYY MM DD" format.

    Box Relayの日付変数の形式に「YYYY MM DD」を使いたい

    Box Relayで日付を変数で入力する際に、「MM YYYY」や「MM DD YYYY」のなどの形式しかないのは不便です。「YYYY MM DD」の形式でも入力できるようにしてほしい。

    11 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)
  8. Inline comments as Trigger in BOX relay workflow

    Currently there is no BOX Relay template to start the workflow with Inline comments as File event. It would be great if there is a template for it or if there is an Inline comment option as File Event in BOX Relay workflow.

    1 vote

    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)
  9. Time added to file names moved by Box Relay

    When moving a Box Sign file in Relay, if the same file is in the folder, the file will be saved with an additional date and time.
    The time added is PST, so if you use it in a country with a time difference from PST, it will be a different time, so it is confusing because it is not clear when it was created.
    To avoid confusion, change this time to the time zone of the Relay owner.

    1 vote

    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)
  10. Relay Trigger "copy out" &"move out"

    In Box Relay, the triggers for “copy” and “move” are recognized as “when a file is copied to this folder” and “when a file is moved to this folder.” Can we create triggers such as “when a file leaves this folder” or "when a file in this folder is copied somewhere else"? In other words, I would like there to be a function that allows us to detect when a file has been copied out to an external folder. I hope this feature will be considered.

    2 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. We want to make it easier to change the owner of a workflow in Box Relay.

    In Japan, organizational changes and personnel transfers occur frequently, which necessitates changing the owner of workflows in Box Relay.
    Currently, to change the owner, users have to transfer the workflow to another user and disable the original workflow.

    This process is not intuitive and is cumbersome for users. Additionally, there are too many steps involved. As a result, even though Relay is a good feature, it feels difficult to use and does not gain user adoption.

    We would like to see improvements that allow for a one-click transfer of ownership.
    For example, adding an option to change the owner in…

    4 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)
  12. Requests regarding BoxRelay: If rejecting, please allow us to enter the "reason for rejection." Although we are substituting by entering it

    Requests regarding BoxRelay:
    If rejecting, please allow us to enter the "reason for rejection." Although we are substituting by entering it in the comments, comments can be deleted.
    Please increase the space between the approval and rejection buttons a bit more. There are times when it causes accidental operations.

    1 vote

    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)
  13. In-platform simple shared calendar feature has been requested for years. Kindly let us know if it is, in fact, off the table.

    Users have been asking for this simple feature for years. Box has been ignoring this request for years.

    I would like to see some accountability to users.

    What is the protocol for communicating user requests up the chain?

    Has this common, years-long user request been reviewed by box's leadership yet?
    If not, please provide a date when it will be reviewed.
    If so, please advise as to what the outcome of that discussion was. i.e., has the request been dismissed permanently?

    Will Box leadership please communicate this clearly to the user community?

    What is the reason for failing to add…

    2 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)
  14. Will BOX ever add a simple in-platform shared calendar feature or can we assume this is off the table?

    Users have been asking for this simple feature for years. Box has been ignoring this request for years.

    I would like to see some accountability to users.

    What is the protocol for communicating user requests up the chain?

    Has this common, years-long user request been reviewed by box's leadership yet?
    If not, please provide a date when it will be reviewed.
    If so, please advise as to what the outcome of that discussion was. i.e., has the request been dismissed permanently? If so, will Box leadership communicate this clearly to the community?

    What is the reason for failing to add…

    2 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)
  15. We want BoxRelay to work with the privileges of the user who actually started the workflow, not the user who created the workflow.

    In the current specification, workflows in BoxRelay operate under the authority of the user who created the flow, not the user who executed the flow.
    This causes confusion because there is a discrepancy with the actual operation performed. We would like to improve this so that Relay can correctly confirm who started the flow.

    【日本語】
    BoxRelayについて、ワークフローを作成したユーザーではなく、実際にフローを開始したユーザーの権限で動作させたい

    現在の仕様では、BoxRelayのワークフローは、フローを実行したユーザー本人ではなく、フローを作成したユーザーの権限で動作するようになっています。
    これでは実際に行われた操作と齟齬があり混乱を招くため、フローを開始した人が誰なのか、Relay側で正しく確認できるよう改善を希望します。

    12 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)
  16. Daily reminders on uncompleted tasks for Approvers in box relay

    Would like to have a function to notify the Approver for uncompleted tasks in box relay on a daily bases. A popup when opening box of the web would also do.

    When the Approver of a task is extremely busy, the current email notification is not enough, therefore would like to have an automatic reminder on a daily bases on pending approval tasks.

    1 vote

    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)
  17. See Shield Policies in Relay View

    See existing Shield Policies when looking at Folder structures in Relay. Shield policies potentially block Relay Workflows, it would be helpful to see if there's a policy and what it is when building Relay Workflows

    1 vote

    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)
  18. Toolbar vanishes randomly

    When multiple files are selected the toolbar goes invisble and right click options are reduced to a minimum. The chance increases with every selected file which makes it practically impossible to move multiple files/folders at the same time.
    Firefox 131.0.3 (64-Bit)

    1 vote

    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)
  19. About Updating Assignee (s) Set to Workflow

    Please improve so that when a user account is deleted by an administrator, it is also automatically deleted from the Assignee(s) in the workflow.

    This is because a deleted user remaining in the workflow Assignee (s) can cause the workflow to stop and cause unintended actions.
    Improvements are needed to ensure that the user's work is not interrupted.

    • in Japanese

    管理者によってユーザーアカウントが削除された際、
    連動してワークフローの担当者からも自動的に削除されるように改善をお願いいたします。

    BoxRelayのワークフローに設定される担当者に削除済のユーザーが残っていることでワークフローが停止されたり意図しない動作が発生する可能性があるためです。
    ユーザーの業務が中断されないために改善が必要です。

    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

    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)
  20. Automatic Data Move without an assigment

    We have created a relay and need a use case where a file, after being uploaded to a specific folder, is automatically moved to another folder. Currently, the relay is only possible when the starter confirms an assignment; we need this without an assignment. The file should be moved after a defined time.

    Details:

    Initial Inquiry: We asked if a relay could be set up to move files automatically after upload without requiring an assignment.
    Box Support Response: Suggested using “A Scheduled Event” as a trigger.
    Clarification: We clarified that the trigger must be the file upload, with the action…

    1 vote

    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)
← Previous 1 3 4 5 19 20
  • Don't see your idea?

Feedback and Knowledge Base