Edwin Engels
My feedback
37 results found
-
1 vote
-
72 votes
Not planned for now. When we update admin login flow in FY20 H2, this will be under consideration.
-
1 vote
-
37 votes
We do not have near-term plans to add this capability right now. You might be able to get a similar effect by using Device Trust on those endpoints and requiring a specific certificate on a device, which is limited to just those groups of users.
-
49 votes
-
30 votes
We are currently focused on building groups for access to 1st and 3rd party apps and specific enterprise settings in Box rather than focusing on groups or individual users for sharing controls. Uservoice request here: pulse.box.com/admin/v3/suggestions/36670615
To achieve granular sharing controls, you can explore using Box Shield to classify sensitive content and set access policies to that content.
-
10 votes
Not currently planned at this time.
-
561 votes
Team is gathering feedback
-
14 votes
-
24 votes
Currently not planned; may be considered for future roadmap
-
165 votes
Instead of “require password” security control, we intend to support “Require OTP” requirement for public links (via SMS, Email, or TOTP). I wanted to share where we are headed. We do not plan on delivering this ask as is, but we do intend to solve the security use case behind it.
Please comment if you disagree.
-
19 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.
-
27 votes
-
30 votes
Not currently planned at this time.
-
72 votes
Not planned as MSFT doesnt have API’s for us to build this integration. Would request all customers to provide feedback to your respective MSFT reps
-
22 votes
Microsoft API’s dont allow co-authoring and MSFT doesn’t plan to support it for Box. Please provide feedback to MSFT reps to enable co-authoring for partners such as Box
-
46 votes
