Matt Stofka
My feedback
216 results found
-
4 votesMatt Stofka
supported this idea
·
-
6 votes
An error occurred while saving the comment Matt Stofka
supported this idea
·
-
122 votes
We are planning on adding the ability to resolve comments in the future, but do not have the ability to like comments as part of the roadmap.
Please keep the feedback & use cases coming to help us prioritize this in the future!
Matt Stofka
supported this idea
·
-
50 votesMatt Stofka
supported this idea
·
-
9 votesMatt Stofka
supported this idea
·
-
60 votes
We have already made sure that the Content remains available to all the collaborators during a Transfer & Delete LFO. We are working on ways to do the same with other forms of LFO. We believe this approach will be a much better productivity accelerator for our customers.
For the purposes of this request to allow for email notification, this still remains in our roadmap to evaluate what would be the remaining use cases that will required an email to be sent.
Matt Stofka
supported this idea
·
-
31 votes
This is currently not planned but we will re-evaluate priorities in Q3/Q4 of FY23
Matt Stofka
supported this idea
·
-
7 votes
I suggest customers look into Shield, a newer Box offering that provides malware detection. If turned on, it scans all content uploaded to Box including the ones from file requests (as well as any file when it's active - e.g., on preview, share, edit, copy, etc. events)
An error occurred while saving the comment Matt Stofka
commented
In response to Anonymous' reply today: while Shield certainly addresses the malicious content referenced in the original post, I think the primary need for email validation is to simply ensure that the person submitting the File Request indeed owns the email address they're entering into the email field that might be required on the File Request form. Anyone can fill out a File Request form and provide any email address without any confirmation that they own the email address they entered. Perhaps Box could text a 6-digit code to the email the user enters and then ask the user to enter that code on the next screen, thereby validating that they own that email. This would then give confidence to the person who owns that File Request folder that the uploader email is correct.
Matt Stofka
supported this idea
·
-
3 votesMatt Stofka
shared this idea
·
-
2 votesMatt Stofka
shared this idea
·
-
10 votesMatt Stofka
supported this idea
·
-
9 votesMatt Stofka
supported this idea
·
-
65 votesMatt Stofka
supported this idea
·
-
5 votesMatt Stofka
supported this idea
·
-
7 votesMatt Stofka
supported this idea
·
-
128 votesMatt Stofka
supported this idea
·
-
141 votes
Thank you for the suggestion. We currently do not have this planned on our roadmap. We will place this in our backlog as we continue evaluating ideas to improve Box Drive.
Please keep the feedback & use cases coming to help us prioritize this in the future!
Matt Stofka
supported this idea
·
-
5 votes
An error occurred while saving the comment Matt Stofka
commented
This can probably be combined with the following suggestion as both involve adding the file id, name, and/or version # into the document footer.
Matt Stofka
supported this idea
·
-
1 vote
Thank you for this suggestion. It is a niche request and I am not sure which problem it solves. We will reconsider with additional use case and demand info.
An error occurred while saving the comment Matt Stofka
commented
I just had a few senior management users ask for this, too. The use case is that if someone prints or emails a file to one of the senior managers (instead of sending a shared link), that the recipient would be able to identify the file name and version just by looking at the document.. Legacy document management systems - such as those used by law firms - have had this feature for decades that puts a document ID and/or version in the footer so perhaps it could be done via the Box Drive or Box Tools desktop apps, or the Box for Office plugin.
Matt Stofka
supported this idea
·
-
7 votesMatt Stofka
supported this idea
·
I'd like to see this added for file names, as well. We potentially have a use case wherein we'd want to outcomes based on File Event > New Upload where file name CONTAINS certain keywords. This use case involves uploading a number of files to a particular folder but they don't want to be notified every time a file is uploaded...only when certain files are uploaded based on the file name.
I explored using File Request and metadata templates for this, but that wouldn't be applicable for this use case; the file name is really the trigger that would determine the Relay outcomes.
Thx,
Matt