Sean Moe
My feedback
10 results found
-
3 votes
While we like this idea, it is not currently planned at this time.
Sean Moe
supported this idea
·
-
9 votes
An error occurred while saving the comment -
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.
Sean Moe
supported this idea
·
-
163 votesSean Moe
supported this idea
·
An error occurred while saving the comment Sean Moe
commented
I just posted a comment on this idea: https://pulse.box.com/forums/909778-help-shape-the-future-of-box/suggestions/36108763-a-way-to-easily-disable-many-shared-links-at-once
My ideal scenario would be to disable public link sharing for all managed users and then be able to enable a few specific users to share links publicly.
Whether it is intentional or not, I have users publicly sharing documents that shouldn't be shared that way. I have no good way to clean up those links and bulk management would be handy.
-
53 votes
Thank you for your input. This idea is considered for future roadmap. Please reach out to me if you like to share your use case.
An error occurred while saving the comment Sean Moe
commented
A couple ideas (we don't necessarily need both of them; either would be helpful):
1) Ability to effectively "reset" all public links in my organization to "people in this folder" but allow users to change certain files/folders back to public if they need it. The idea here is that I'm an admin and whether intended or unintended, I have users making files available publicly that shouldn't be. I want to allow my users to share certain files/folders publicly, but over time we accumulate links that shouldn't be public. I want to do a hard reset on all publicly shared links to be sure nothing is getting leaked. Yes, it forces those who have legitimate needs for public links to go re-share them publicly, but that's easier than going through each file one-by-one to disable it.
2) I want to disable the ability to share links publicly for the majority of my managed users and have just a few that have permissions to share publicly. This is better than #1 because then I don't have to periodically mass-reset all public links. I can be sure that the few who can share publicly are trained to use it responsibly.
Sean Moe
supported this idea
·
-
381 votesSean Moe
supported this idea
·
-
6 votesSean Moe
supported this idea
·
-
37 votes
An error occurred while saving the comment Sean Moe
commented
One question that Box's support team wasn't able to answer for me is whether there have been spikes in failed requests against my enterprise domain (possibly indicating an attack). As we've learned about data loss at Apple, Amadeus, Discovery, etc. due to publicly shared links, we've wanted more data about whether or not we've been susceptible. The Shared Links report tells us what's been made public and the usage report tells us some about who has successfully accessed files. What we don't know is whether there have been large spikes in unsuccessful request (indicating someone might be trying to guess public links). While it may not answer all my security-related questions, including metrics around successful vs failed link requests against my domain could be helpful.
Sean Moe
supported this idea
·
-
33 votes
As we work to build out a more robust compliance framework, this is absolutely something we’ll be considering. However, it is not on the near-term roadmap.
Sean Moe
supported this idea
·
-
96 votes
Due to other higher priority items, this has been deprioritized.
Sean Moe
supported this idea
·
I could be misunderstanding, but I believe your Enterprise Account settings already allow you to change the shared link default to "People in this folder". We have it enabled on my organization's enterprise account, so users have to explicitly designate a shared link as public before it is public.