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.
209 results found
-
Localize the name of "Classification" metadata template to user's language
User cannot name of "Classification" metadata template which is automatically created when the user create Classification policy. At least it should localize to Box admin's language (ex "分類" in Japanese)
2 votes -
Increase the maximum number of Shield Classifications beyond 25 so that we can classify each clients content to prevent mis-sharing
I would like to see the ability to add Shield Classifications per client - with the appropriate access policy (restricting to client email domain) we could avoid any possibility to overshare when inviting the wrong clients into a folder or sharing a shared link - There is a maximum number of classifications of 25 so could this be extended to facilitate this use case/control.
25 votesWe will have a different solution to address the use case.
-
Classification definition
Currently when classifying a document it is only possible to see the top 2-3 lines and is not rich text therefore doesn't support returns, bold type, links, bulleted lists or colour.
While the full 300 characters are displayed in the details pane, Users need to see all the details prior to applying the classification.REQUEST: To make the dropdown either expandable (i.e. 'show more') or to show the full 300 character classification definition and to make the definition field 'Rich Text' so its possible to give more context to the classification e.g. provide a list of example documents or link…
4 votes -
4 votes
Not a priority. Will revisit in 6 months.
-
We want the ability for Download policies to also trigger on unusual download activity by external collaborators
We see external collaborators with high download activity using accounts outside of our enterprise (ie: gmail, yahoo?). The business is getting quite frustrated that they cannot report on these email addresses.
3 votesThis is quite complex to implement, we are researching to figure out how best to fix this.
-
Selectively disable syncing to mobile and desktop based on content classification and/or user group.
0 votes -
Granular permissions per user for sharing public links/classified documents
The administrator should be able to set the default classification for all new documents (e.g. For Official Use).
Each user should be able to set their own default classification (which will override the system setting (e.g. Classified).
Each user should be able to change the classification for any new or existing document where she has sufficient rights. For existing documents, she should also be able to select multiple documents, and then change the classification for all those documents in one go.
1 voteDefault classification label is not planned because it could be misleading to end users. However, to address the concern of content being leaked before it is classified, you can create an access policy applying to “All content without a classification label” in Box Shield.
-
Set default classification for all uploads with Box Classification
When every file is uploaded, set a default Classification value that can be updated manually or via a partner (Netskope, SkyHigh, Titus, etc.).
13 votesDefault classification label is not planned because it could be misleading to end users. However, to address the concern of content being leaked before it is classified, you can create an access policy applying to “All content without a classification label” in Box Shield.
-
Events API - Add Policy Name to CONTENT_WORKFLOW_UPLOAD_POLICY_VIOLATION
Currently, when an Upload Policy violation occurs, Box reports on that violation in 3 ways:
1. Email notification
2. Admin Console -> Reports tab
3. Events APIIn the email notification and admin console->reports, Box provides the policy name for which the violation is occurring. However, Box does NOT include the policy name in the Events API entry, which causes a problem when we are pulling logs (via the Events API) into external reporting/SIEM tools like ArcSight/Splunk.
Request: Add 'Policy Name' to the CONTENTWORKFLOWUPLOADPOLICYVIOLATION entry in the Events API (to reach parity with the native Admin…
1 vote
- Don't see your idea?