Anonymous
My feedback
7 results found
-
23 votes
For now, we are focussed on solving bulk management issues with Shared Links.
Box Shield is an additional option for enforcing granular controls on content.
An error occurred while saving the comment Anonymous
supported this idea
·
-
89 votes
We have considered this but this is not on our roadmap currently
Anonymous
supported this idea
·
-
14 votes
An error occurred while saving the comment Anonymous
commented
It would be good to at least add an option to justify the text. Currently, only a few HTLM tags are supported that do not guarantee the text to be visually appealing.
Anonymous
supported this idea
·
-
88 votesAnonymous
supported this idea
·
-
25 votes
We are targeting a solution to be released in the calendar year 2025. Please reach out to learn more!
Anonymous
supported this idea
·
-
24 votes
Currently not planned; may be considered for future roadmap
Anonymous
supported this idea
·
-
317 votes
This suggestion is under consideration by the Product Team for future development, however, it is not on our roadmap. Please share additional feedback and use cases to help us understand the importance of this release.
Anonymous
supported this idea
·
This idea also matches our requirements for Shared Links.
We would like to have better granularity for this setting. Currently, we can only enable public shared links for the entire BOX instance or disable it for everyone. While we do not want to grant everyone the possibility to create publicly available shared links to avoid unintentional data leaks, there might be justified use cases where password protected open links are needed.
We would like to have an option that either only Admins can create shared links or a kind of approval process before a public link can be opened.