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.
416 results found
-
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.
誤操作により、本来権限を付与されるべきではないユーザーがコラボレートされてしまう可能性があるため、
チェックボックスのチェックを任意で外せるようにしてほしい。31 votesWe are conducting user feedback sessions to gather more information
-
File request - Allow only Manage Users from an EID to upload via File Request
In file request, have the ability to state that only a managed user in the EID or an external user that has been invited to the folder can upload, no one else. By doing this, it prevents a file request link from being randomly guessed or found on the internet AND prevents a random user from uploading bad or malware/virus infected content. The current state of requiring the user to login is too generic and doesn't meet the requirement of keeping the file request locked down. Using the collaboration role for upload is not what is needed. The File Request…
30 votes -
We would like to be able to register a group in the Configure Relay even if the group's permission setting is not "Administrators only"
Currently, when we try to register a group in the Relay configuration, we can register the group if the group's permission setting is "Administrators only", but not if the group's permission setting is "Company" or "Group Members".
Registration location [Enterprise Settings > Content & Sharing > Configure Relay].
We are using "Company" and "Group Member" as the permission setting for groups to be able to respond to group invitations, etc. outside of the management console, so we would like these permission settings to be able to be registered in the Configure Relay.<グループの権限設定が「管理者のみ」以外の場合もBoxRelayの構成でグループを登録できるようにしてほしい>
現在Relayの構成でグループを登録しようとするとグループの権限設定が「管理者のみ」の場合は登録できるが、
「会社」や「グループメンバー」の場合は登録できない。【Enterprise設定＞コンテンツと共有＞Relayの構成】
グループの招待など管理コンソール以外でも対応できるようグループの権限設定を「会社」や「グループメンバー」として利用しているため、
これらの権限設定でもRelayの構成で登録できるようにしてほしい。29 votes -
box relay shared link
Using Box Relay, create the following new outcome: Based on a metadata value when stored on on a file or folder, create and share a web link to the email address(es) in the metadata value, with specified collaboration.
28 votes -
Generate Shared Links as a Relay Outcome
Would like the ability to automate generating shared links on files within Box Relay as an outcome. One use case for this would be to create a process for generating external shared links. Many security-conscience customers don't want everyone to have the ability to shared content externally without some sort of approval or oversight. If we added generating and sharing shared links as an outcome in Relay we could build approval flows that would allow users to get approval to share a file externally even if they don't have the access do so.
27 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.
26 votes -
Name in the notification email of Box Relay should be the initiator of a workflow rather than workflow owner/creator.
Currently the name displyaed in the notification email of Box Relay is the name who owned/created the workflow.
It's idal to be displayed Name of initiator of a workflow in the notification email especially in caseunspecified majority of people might launch the workflow by manual.
Enabling the above feature makes it much easier to confirm user who start the flow.25 votes -
When copying or moving a file via Relay, allow the file to overwrite an existing file of the same name as a version.
If we have a locked down area for SOP type files, as the SOP is updated and approved, a Relay workflow moves the file into the published location. If the published file is the same name as an existing file, we would like to have the new file come in as a version of the prior file, not be named with the date-time stamp on it.
25 votes -
Relay Workflow period Allocations based on work days rather than natural days (i.e Exclude Weekends)
When assigning a task in relay you can assign the period in days associated to the task. at This point in time this does not allow the option to assign such days to working days but only natural days. Therefore if and when a weekend occurs during the timeline of the workflow action weekend days (non-working days absorbs the task timeline. the request is that there must be an option to assign a task only for working days (excluding weekends)
25 votes -
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)
通知の相手に割り当てられたユーザーへの通知の際にファイル名を含めた通知を行いたい。
通知を受け取ったユーザーが通知メールを受け取っても、どのファイルに対する通知なのかを
簡単に確認できるようにしたい。23 votesWe are conducting user feedback sessions to gather more information
-
Ability to comment on Box Relay approval tasks
Currently, there is no function to enter comments when executing approval tasks using Box Relay.
We are currently using email and the Mention function, but this is inconvenient, so we would like to have the ability to enter comments at the time of approval or rejection.
Having a comment when approving or rejecting a task will help us communicate with users, so we would appreciate it if you could add this as a feature.
現在Box Relayを利用した承認タスク実施時に、コメントを記載する機能がありません。
メールやメンション機能を現在は利用しておりますが、不便なため、承認時または却下時にコメントを入力する機能が欲しいです。
承認時や却下時にコメントがあることで、ユーザーへの意思疎通ができますので、機能として追加をいただけますと幸いです。23 votes -
Relay：Users who have already been invited in a group will not be invited with "Invite assignees as Viewers/Editors"
[Background]
A new feature has been added to Relay called "Invite assignees as Virwers/Editors".
"Invite assignees as Virwers/Editors" are sent to users who have already been invited in the group.
This is confusing because additional invitations are carried out to users who have already been invited.
Furthermore, operationally, this requires the collaboration to be removed from the relevant file each time.
*As a company rule, we are not allowed to collaborate with individuals individually, except in groups to which they have been previously invited by Admin.[Request]
Users who have already been invited to a group should not be invited.…
23 votes -
Be able to specify a document or a shared link in “Send Notification” outcome
It would be convenient if the “Send Notification” outcome had an option to specify a document or a shared link in the notification body.
Right now it is only possible to input plain text.
23 votes -
Have Docusign integrated with Relay
Use Relay+Docusign to manage contract approval process
23 votes -
Relay: Involve external Users to a manual workflow as "not-owner" of the folder/file
Hi,
i discribe a situation:
The Admin is the owner of all folders/files, directors has co-owner-rights and all employees are editors. It is similarly discribed in "Folder Structure Best Practices" under "Business Unit Drive"
Now we invite some external users... not only the owner can invite them.
Then we create some relays for specific folder, especially some manual ones, assign a task and set the Assignee to "Specify at startup"...not only the owner can do this.
Last but not least we start the manual workflow and choose as Assignee an external user... but wait...ONLY the owner of the folder (1…20 votes -
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」の形式でも入力できるようにしてほしい。
19 votes -
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 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側で正しく確認できるよう改善を希望します。18 votes -
Box Relay outcome to Apply Classification to a folder dynamically
It would be helpful if Box Relay would have the ability to apply a classification to the folder where the workflow was triggered on dynamically as an outcome, which would also classify all content within that folder structure as well. This would allow applying classifications to the folder that a new file event trigger happened in for example, which would then flow classifications to all content and sub-folders in that folder structure.
17 votes -
Allow service accounts to initiate Relay workflows via the Box API
Allow service accounts to own and initiate Relay workflows via requests to the Box API
17 votes
- Don't see your idea?