Our admins are constantly dealing with users who accidentally drag and drop folders into other folders. This can have a big impact across our org, especially when a high level folder that's shared across the company is moved. Here's a common use case:

We have a top level Projects folder. That folder contains a subfolder for every organization we do business with. Those Organization folders then contain subfolders for individual projects. We'd like to be able to mark the Organization level folders as Move Locked so that our users don't accidentally move folders from one Organization into another. This happens constantly in Box Drive.

The idea would be that an admin can mark a folder as Move Locked, and the folder would be identified with an icon letting users know that it's move locked. The only way to move it would be for an admin to unlock it first.

The login page is very confusing for our external collaborators. Despite the creation of "How to log on to Box" with pictures, external collaborators still click on the wrong link as the "Continue" button (for our managed users) is very large compare to the small font link for the external collaborators. The natural instinct is to click on "Continue" which gives the external collaborator an error since they are not part of the "managed users" and will not be able to SSO to our Box. Our staff is having to help our external customer on regular basis.
Can the login page be modified to have 2 customizable buttons: a "[Company] employee" and "Not a [Company] employee" where [company] is a variable for each Box Enterprise customer to type in the name of their company.

Assume I have a metadata template "Template" with a key - value of type Number. In both the web app and API, it is not possible to do an equality search:

templateKey = template
filters = {"value": 2}

Instead, the search requires specifying both lower and upper bounds. If you're searching for a single value, you then have to approximate it with a gt = 2, lt = 2 combo.

a) Most importantly, the API documentation implies that the range parameters are not required when searching by number or date.

b) I think both the webapp UI and the API should allow equality searching for number and date; i.e., ID = 2815