Skip to main content

Trying to create an approval workflow as follows:

User attempts to share a document (within a specified folder)


Manager is notified for approval (approves or denies)
Final Approver (approves or denies)


( during the approval process, the document is not shared to the recipient )
( if at any point the document is denied, the party initiating denial should be required to fill supply the denial rationale )


Share is approved & sent to intended recipient.

###End of Workflow.

I do see similar logic to the above in Box relay, but the concerns are as follows:
File Action 'Add Collaborator'
- if I were to put this as the initiating event, this action implies that the external Collaborator has already been added, however the recipient field needs to be pre-defined (see bottom bullet)


- if I were to put this action at the end of the workflow, the share initiator would need to revist the workflow, however the recipient field needs to be pre-defined (see bottom bullet)
- most concerning, is that the 'Add Collaborator' workflow requires a pre-defined recipient field, making the workflow of null value for a share approval workflow component. As you would expect there to be a variable option for 'user defined recipient' or some such verbiage.

Hi there, 


Welcome to the Box Community!


This would be something Product Support team would like to investigate and may require specific account information. I see you already have an open ticket for this issue, please continue working with them and check your email for updates.


Thank you for posting!


I have an open ticket that is related to workflows, but is not scoped to / directly associated w/ the contents of this post.

This support forum item may have been answered by Box staff, but is not resolved / has not been addressed.


Reply