Anonymous
My feedback
73 results found
-
3 votesAnonymous
supported this idea
·
-
18 votes
Interesting suggestion, but we won’t be focusing on this ask for the time being due to competing priorities.
Anonymous
supported this idea
·
-
5 votes
This is not something we will build due to other roadmap commitments.
Alternatively, you could always upload latest version to “backup folder,” delete file from “current version” folder, then copy “backup folder” version to “current version” folder.
This will get you 100% version history in backup folder and avoid the need to download & upload the file a second time.
Anonymous
supported this idea
·
-
26 votes
Although we do not plan to introduce this feature in the near term, we recognize its importance. We will certainly keep this in mind for future roadmap inclusion and we will keep the status of this request updated to accurately reflect our current position.
Anonymous
supported this idea
·
-
163 votes
An error occurred while saving the comment Anonymous
supported this idea
·
-
18 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.
Anonymous
supported this idea
·
-
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.
Anonymous
supported this idea
·
-
11 votesAnonymous
supported this idea
·
-
20 votes
An error occurred while saving the comment Anonymous
commented
I also wish there was a way to use copy vs. move that would capture file version history and allow us to have a point in time copy, that we can still allow users to view, but not allow them to edit content for all existing collaborators.
Anonymous
supported this idea
·
-
44 votes
We now have the ability to use TOTP for 2FA. In addition, admins can enforce TOTP for managed/external users.
We do want to support FIDO standards for 2FA in the future and will update this idea with more details once we have a concrete plan.Anonymous
supported this idea
·
-
80 votesAnonymous
supported this idea
·
-
2 votesAnonymous
supported this idea
·
-
4 votes
It will be super helpful to understand the business impact to report on who deleted from trash. At this moment, admins can configure rules to delete trash after a certain period time. This doc would be helpful: https://community.box.com/t5/Managing-Files-and-Folders/Trash/ta-p/19212
Anonymous
supported this idea
·
-
4 votes
This is an interesting feature! However, it does not have enough demand or impact in order to be prioritized. We will reconsider with additional demand.
Anonymous
supported this idea
·
-
9 votesAnonymous
supported this idea
·
-
1 voteAnonymous
supported this idea
·
-
5 votesAnonymous
supported this idea
·
-
8 votes
We don’t currently have this slotted in as an update to the Trash page given limited asks for it. If customer demand persists, we will re-evaluate, though this change also requires an API update since https://developer.box.com/v2.0/reference#restore-a-trashed-item only allows choosing of a new target parent folder in the case where the original parent has been deleted or user lost access.
Anonymous
supported this idea
·
-
31 votesAnonymous
supported this idea
·
-
1 vote
Default 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.
Anonymous
supported this idea
·
If we want to change all our shared links from Editor to View Only would be nice as well. We have found cases where we need to do this throughout a folder structure. Having the ability to force that change from a top level folder on down would be really nice.