Anonymous
My feedback
4 results found
-
1 vote
An error occurred while saving the comment -
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 Anonymous
commented
This is a big issue. There is virtually no "forensic" capability related to links. There is no report that shows who created a link (the report only shows content owner) and once a link expires or is deleted there is apparently *no record at all*. It's just gone.
In the current age of cyber securit, logging requirements, non-repudiation, etc this is unacceptable.Anonymous
supported this idea
·
-
4 votes
An error occurred while saving the comment Anonymous
commented
I can't believe this doesn't get more votes. The lack of the ability to break inheritance is a major problem within Box.
This should really be a basic feature. It's always spun as a consequence of "waterfall" permissions, but it doesn't really have anything to do with "waterfall". Lots of systems with "waterfall" permissions can also break inheritance.Anonymous
supported this idea
·
-
29 votes
We are investigating the best options to implement this into our Threat Detection alerts and dashboard.
Anonymous
supported this idea
·
If this is ongoing, I'm up for it.