Matthew Ryan
My feedback
92 results found
-
13 votes
An error occurred while saving the comment -
445 votes
We understand the request, but unfortunately this is not on the near-term roadmap.
An error occurred while saving the comment Matthew Ryan
commented
Playing with fire here. Years of user decisions in a non-waterfall environment accumulate a massive set of permissions exceptions that become a headache for everyone. If implemented, "allow breaking waterfall" should be a folder setting, with defaults managed in the Admin Console.
-
21 votes
Thank you for the feedback. We have noted this feature request and understand the value of this feature. Unfortunately, it is not on the current roadmap.
Matthew Ryan
supported this idea
·
-
2 votes
An error occurred while saving the comment Matthew Ryan
commented
If a collaborator is invited just to a subfolder, that will appear as a root folder to them.
-
7 votesMatthew Ryan
supported this idea
·
-
29 votesgathering feedback · 6 comments · Help shape the future of Box » Core & Technical Infrastructure · Admin →
An error occurred while saving the comment Matthew Ryan
commented
Use Viewer Uploader role instead of Editor role? (Viewer Uploader can edit files but has much less freedom to make other changes.)
-
73 votesMatthew Ryan
supported this idea
·
-
4 votesMatthew Ryan
supported this idea
·
-
31 votes
Thanks for the suggestion! This is not currently planned, but we will keep it in mind for future enhancements of the product.
An error occurred while saving the comment Matthew Ryan
commented
I support allowing Editors to remove someone else's lock, because people locking the file make mistakes and the person with the problem to solve knows they are making a judgment call.
If you don't want people to have this ability you can change them to the Viewer Uploader role -- which can still edit the file, but would not be able to override a lock on that file.
-
7 votes
Thanks for your feedback. It’s called Box Tools because it actually contains both Box Edit and Device Trust capabilities in this one installer.
Matthew Ryan
supported this idea
·
-
8 votes
We’ll keep this in mind! However, this is not currently planned.
Matthew Ryan
supported this idea
·
-
10 votesMatthew Ryan
supported this idea
·
-
9 votesMatthew Ryan
supported this idea
·
-
4 votesMatthew Ryan
supported this idea
·
-
6 votesMatthew Ryan
supported this idea
·
-
13 votesMatthew Ryan
supported this idea
·
-
5 votes
An error occurred while saving the comment Matthew Ryan
commented
Consider restricting external collaborators to "Viewer Uploader" (which can edit files but not delete) rather than granting them full Editor access. MFO functionality is not available for access levels below Editor.
-
7 votes
An error occurred while saving the comment Matthew Ryan
commented
Rather than allocating a new Box account to the same person, wouldn't it be better to change the name and primary email address of the existing user? This would preserve collaboration access and also have a consistent identity for that user in all reporting, since they'd retain the same unique id under the hood.
-
15 votesMatthew Ryan
supported this idea
·
-
4 votesMatthew Ryan
supported this idea
·
Probably not implementable because names of parent folders can contain confidential information. eg you could have your client folders moved between different areas depending on how they're being managed, without intending to telegraph that to the clients.