FEATURE IDEA:
Provide ability to flag/classify files and folders in a way that allows Box to move them to a less-expensive storage offering on the back-end. This can be referred to as an "inactive" or "archive" flag.

BENEFITS & BACKGROUND

During the Box Higher Education Community Monthly Open Discussion on January 11th, an idea to submit to Box Pulse was formed, and seemed to have support from all in attendance (25-30 institutions).

Box acknowledges that there is a growing concern around constantly increasing storage, and the costs associated with it. The majority of files stored in Box are perceived (or actively reported) as being "inactive" and yet those files are costing Box and their customers the same amount. As a result, organizations are searching for alternative cost-effective solutions to move their data into. Implementing a separate solution for a subset of Box data requires significant technical, administrative, procedural, and support overhead.

Given a user or admin-driven active/inactive flag, Box could engineer their platform to use cheaper back-end storage for inactive data, and more permanent storage for active data, ultimately providing a more cost-effective service.

Administrators could be given the ability to set the parameters for what makes something an "inactive" file, and then allow end-users to tag their own content.

Allowing a view and controls around "active" vs "inactive" content, means Box could then provide X amount of "active" storage, and Y amount of "inactive" storage quota either included in the price, or for an additional fee (at better a less-expensive per TB rate). Organizations can then choose to deploy the associated quota controls and processes based on their own budget and needs for active and inactive storage.

Market opportunity -- other cloud  providers do not provide user-initiated controls for this kind of approach to data storage and management. If the providers are implementing anything like this, it is not transparent to the user. Box may have an opportunity to retain users and their data, by providing a more cost-effective glacier/cold-line/archive/inactive data storage offering, side-by-side with the rest of the Box platform.

When a user clicks the email button the Share Link screen they have the ability to enter an optional message to the person they are sending the link too. This optional message is not captured anywhere in the Box system or event stream. The only way to capture a record of this optional message is with the Compliance Email Archive. Customer would like for this optional message be captured in the event stream so 3rd party compliance software can capture that information. This is an issue in regulated industries like Wealth Management in Financial Services that require logging ALL potential messages that may go to a customer.

Usually when you go "in" or "down" a level by opening a folder or a file within that folder, there is some sort of "go back" feature in Box itself like a file path where you can click back out to the parent folder or an X to close a document. But when you click on the icon to show you who the collaborators on a document are, it seems the only way back is to use the browser's back arrow.
(Also it would be even better to simply show the list of people who can access the file at right the same way it shows up for shared folders. Then you don't have to click into anything.)

The "Notification Email" functionality in Box is very helpful for @mentions, file sharing invites and other user notificaitons that need to go to an email address other than the email address used to sign into Box. This can be the necessary when a company has subsidiaries on a common directory infrastructure, but one or more subsidiaries is still maintain the old email identities for day to day work. There are likely other reasons to use this field.

Email: john.doe@mothership.com (Used to sign in.)
Notification email: jdoe@subsidary.com (The correct email address for user notifications.)

Box's SAML integration allows an Identify Provider, Okta for instance, to provision a new user which is great. However, it's not presently possible to populate the data element for "Notification Email" via SAML. This requires a time consuming manual update in Box when setting up a new user.

It is not a feature of Box to allow "file audit logs" to persist on files showing a deleted users name as the person who made the changes and currently when you remove a user all the collaborators (non-admins) can see is "user made change" instead of the person's name. Yes, you can pull a file management report, but that is for admins and does not provide the teammates of the file any insight as to who was the person that made this change, nor does it help admins determine it easily either. I would like for the product to incorporate persisting this data on all files, even if a user has been fully removed from the tenant. The change logs should persist indefinitely on a file whether a user is active, inactive, or removed.

【Background】
As we use many Linux servers, the total size of the log files is also large.
Please add Linux as supported, as we want to save the log files stored on the Linux server to the Box.

【Request】
Box does not support Linux.
In the past it was possible to access the Box via WebDAV, but this is no longer supported.
Please add Linux to the support for Box.
It would be preferable if it could be mounted like WebDav.
If the folder on the Box can be mounted on Linux, the application can simply change the specification of the directory as a destination for the data, without being aware of it.

【背景】
多くのLinixサーバーを利用しており、そのログファイルの総サイズも小さくありません。
Linuxサーバに保存されているログファイルをBoxに保存したいので、Linuxをサポートとして追加してください。

【ご要望】
BoxはLinuxをサポートしていません。
過去にはWebDAVによりBoxへアクセス可能でしたが、現在はWebDAVの利用もサポートされていません。
BoxのサポートにLinuxを追加してほしい。
WebDavのようにマウントできることが理想です。
Box上のフォルダがLinuxでマウントできれば、アプリケーション側では意識することなく、ディレクトリの指定を変えるだけで、データの保存先として指定できると思います。

File uploads are extremely slow. For example, a group of 3 x 20Mb files might take an entire day to upload on a 5mb.s connection. This has happened in the past 3-4 weeks.
I found the root cause of it. I am in New Zealand and redirected to the Tokyo server, which is very very slow. I verified that this upload path is an issue thus:
Tried to upload a 20Mb file using browser (via Tokyo) - 2 hrs later the file was at 20% upload. Cancelled the upload.
Connected a VPN onto Los Angeles. Uploaded the same file (and others). Uploads completed in less than a minute.
This performance issue forces me to use a VPN each time I use Box to upload which is burdensome.

Thanks for your attention on this.