Help shape the future of Box
Welcome to Box Pulse, our product feedback tool powered by UserVoice. Got an idea for how to improve Box? Share it with us and gather support or vote on other people's ideas. Your feedback is essential to informing roadmap decisions and shaping the future of our products. Thanks for joining our community!
See user guide here.
6 results found
-
Access policies for individual folders
Would it be possible to set up access policies that can be applied per-folder instead of by Classification label?
We have Ethical Walls and security concerns where we need to prevent sharing of files of Client A with Client B and also with preventing individual users from being shared folders.
One way to do this would be classification policies - but I have far more clients than the twenty five label limit.
The way around this would be to allow access policies by folder, regardless of classification, as well as the Box-wide access policy for unclassified content.
Client A -…
7 votes -
Box Shield - reporting option within UI to export past Threat Detection Alerts
In addition to the Shield Dashboard, an option to export all past threat detection alerts
16 votes -
Require approval when sharing content with a business justification
Current access policy allows for external collaboration with a valid business justification, but we would also like to have the admin or folder owner approve the request to share externally, before the collaboration is sent. The current design doesn't allow for any validation and could potentially lead to content being shared with a restricted audience. Once the exception is approved, the collaboration could be set.
32 voteson longer term roadmap.
-
Shield Shared Links: Password Requirement
Passwords for public links are wonderful, however, the capability to enforce all links (even those with internal or collaborator scope) would be beneficial for users and content security. If this password requirement could be tied to classifications as an access policy, that would make it increasingly difficult for negligent or malicious actions on Box content. Currently, we can only decrease the scope available for shared links, but by requiring a password, there will be additional adoption for Box and Shield, especially within highly regulated industries that require external or public distribution of content.
23 votes -
Restrict Collaboration for Individual External User
Customer would like to have the ability to block individual external users from collaborating on their enterprise content. The external domain allow list is too broad if only one or two external users need to be blocked from collaborating on content.
11 votes -
Shield Alert - mark as resolved
On the dashboard for Shield, you see a list of alerts generated through threat detection policies. We'd like to see the functionality where end users could mark an alert as seen and/or resolved so everyone who monitors the Shield alerts would know whether it's been resolved or open. This is similar to a ticketing system, but a simple notes body on the alert where someone could put an explanation of their response to the alert would greatly enhance visibility and drive better usability. Thanks!
24 votes
- Don't see your idea?