Custom branding for file request feature. Ability to apply one custom branding template to the entire EID so that the branding is consistent across the entire enterprise.

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.

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.

Would be great to be able to add a group of collaborators “Add Collaborator” outcome. Right now only single users are accepted as input.

Relay search is hard to use (cursor pointer disappears while typing)
This happens only in end user panel, admin search is not affected

Relay is a great tool - but the Notifications aren't very useful. There is no way to link to the actual file or folder that is involved, so the user gets a very nebulous notification that is basically meaningless. Instead of being helpful, it could actually cause confusion for the user, if there are multiple activities happening at the same time.

Please update this functionality! Thanks!

Currently there is only delete option to stop the workflow.
Workflows are stalled or stacked as in progress sometimes. We want to assign similar task manually or re-assign the same task to complete the workflow in time.
But it will cause duplicated tasks assigned unexpectedly or file operation (move or copy etc.) is executed twice. This is very confusing.
So we want to cancel the existing workflow before manual workaround.

Box needs to add the cascade option to all Relay triggers to catch activity in underlying subfolders. The alternative is having to create several relay workflows that is too cumbersome to manage and doesn't scale.

We have a manual start workflow where we want to collaborate a volunteer to a template folder where they need to fill out some forms and upload back to a Box folder. Relay does not seem to let the workflow starter enter the collaborator's email UNLESS they already exist as an external user.

Box Relay creates a workflow (Folder creates a task that requests invoice processing and is used to manage outstanding tasks) that enables clerical employees to process invoices more efficiently. However, when the employee is transferred, the workflow that has been created is not transferred to the next person in charge. If a useful workflow can be managed as a company, not as an individual (Change the workflow owner for contact changes), it will be very useful for business efficiency.

Currently, no matter what timezone users/enterprise set in its settings, the PST timestamp will be added to the item's name when conflicting name on Relay.

The specification will be changed to add the date and time depending on the user/enterprise settings.

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.

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

Enable file requests at a folder level to restrict internal-only folders vs. not. There are existing folder-level settings that can restrict external collaboration and what type of shared link can be crated, but the same ones don't exist for File Request links. It would be great to have the same feature parity between shared links and file request links when wanting to restrict access.

There is an option “Specify when started” in “Assign a task” outcome. It would be convenient to have a similar option in “Send a notification” outcome, since the recipients might vary depending on who started the workflow.