Masahiko
My feedback
34 results found
-
6 votes
An error occurred while saving the comment Masahiko
supported this idea
·
-
1 voteMasahiko
shared this idea
·
-
2 votesMasahiko
shared this idea
·
-
2 votes
An error occurred while saving the comment Masahiko
commented
We would like each user to be able to check off their own progress as a viewer. Administrators should be able to create and manage onboarding checklists as editors in the Hub, as well as track and report on each user's progress. If this is possible, it could serve as an alternative to an e-learning system and encourage more people to use the content.
Masahiko
shared this idea
·
-
5 votesMasahiko
shared this idea
·
-
7 votesMasahiko
shared this idea
·
-
7 votesMasahiko
supported this idea
·
-
8 votesMasahiko
supported this idea
·
-
6 votes
This feature is not yet planned for hubs.
Masahiko
supported this idea
·
-
9 votesMasahiko
shared this idea
·
-
54 votesMasahiko
supported this idea
·
-
1 voteMasahiko
shared this idea
·
-
74 votesMasahiko
supported this idea
·
-
6 votesMasahiko
supported this idea
·
-
12 votesMasahiko
supported this idea
·
-
11 votesMasahiko
supported this idea
·
Masahiko
shared this idea
·
-
24 votesMasahiko
shared this idea
·
-
113 votes
Due to other higher priorities, we are not considering this item at this time.
Masahiko
supported this idea
·
-
44 votesMasahiko
supported this idea
·
-
7 votesMasahiko
supported this idea
·
Strongly agree — this is a real gap for security-first deployments.
We've disabled Box Drive across our entire tenant as a deliberate security control, and no one in our organization uses it. But that control only reaches our own users. External collaborators can still mount content we've shared with them via Box Drive on their own machines, and as admins we have no way to prevent it.
That's the problem. We have no visibility into how an external user's Windows device is managed — patch level, EDR coverage, disk encryption, local admin rights. Once our files are synced down to an endpoint like that, a compromise on their side becomes a compromise of our data, through no fault of our own controls. We can harden our devices; we can't harden theirs, and today we can't opt out of the risk either.
Security was the primary reason we standardized on Box, so it's frustrating that this one path is outside admin control. An enterprise-level setting to block Box Drive access for external collaborators (ideally with per-folder or per-collaboration granularity) would close it. This is a high-priority need on our side, and I'd expect it matters to any customer in a regulated or security-sensitive industry.