Help shape the future of Box
Welcome to Box Pulse, our product feedback tool powered by UserVoice. Got an idea for how to improve Box? Share it with us and gather support or vote on other people's ideas. Your feedback is essential to informing roadmap decisions and shaping the future of our products. Thanks for joining our community!
See user guide here.
- or
No existing idea results
- ~ No ideas found ~
9867 results found
-
Request: Rich Shield dashboard
Request for Shield Dash board
The information of the graphs is so simple.
Could you make the rich insight?
For example, whne the targeted user who caused anomalous download started downloading a lot f contents, how much increased #s of DL day by day, Week by week etc.Currently we need to export user activity report if we want to know more. so rich insight will be helpful for Box admin.
5 votesThis request is being evaluated alongside our other Shield Dashboard asks as we target improvements for 2026.
-
Ability for Admins to find the owner/creator of a custom app, regardless of auth type
Admins should be able to find out who created an application. Right now we can only see the authentication types that are authorized through the admin console. OAuth applications are not easily researched. If the application was created outside of the 7 year reporting window, we also aren't able to create an activity report to determine which user created the application. If an app is making calls in our Enterprise, we should be able to figure out who owns the app in case there are any issues and they need to be contacted.
1 vote -
Request for improvements to Box folders for Teams in Box for Teams V2
When using Box for Teams V2, we found that the auto-created folders for teams were heavy on operations.
I would appreciate it if you could add the following two functions.
1.When you delete a member from a team, you want to delete that member's collaboration from the team Box folder.
2.When the team itself is removed from Teams, remove all member collaborations from the team Box folder.1 vote -
API) Add 'enterprise.id' to the collaboration user object.
When retrieving the list of collaborators, we want to know whether each collaborator is an internal or external user, like in Box Web.
The collaborators object does not include information to determine whether a collaborator is internal or external user. As a result, we have to call the Users endpoint, which increases processing time.
API Call:
GET https://api.box.com/2.0/collaborations/:collaboration_idWe would appreciate it if the EID could be included in the collaboration response to improve efficiency.
1 vote -
Require comments when changing classification labels and keep history
Require comments when changing classification labels and keep history
Currently Box Shield does not allow the reason or history to be kept when changing.
We would like to see a comment input field added to the UI when making changes, and also made mandatory in the administrator settings.If it is a file, we would like to leave the comment entered in the comment (activity) field of the file so that the end user can check the history.
For folders, we would like to leave them as undeletable txt files, etc.Such a feature would allow all users above the editor level to be allowed to change classification labels, thus maintaining convenience and increasing voluntary security awareness.
in Japanese below.
分類ラベル変更時にコメントを必須にし、履歴を残す現在のBox Shieldでは、変更時の理由や経緯を残すことができない。
変更時のUIにコメント入力欄を追加し、管理者設定で必須化もできるようにしてほしい。入力されたコメントは、ファイルであればファイルのコメント（アクティビティ）欄に残し、エンドユーザーがその履歴を確認できるようにしたい。
フォルダの場合は、削除不可能なtxtファイル等として残したい。このような機能があれば、編集者以上のすべてのユーザーに分類ラベルの変更を許可できるようになり、利便性の維持と、自主的なセキュリティ意識の向上につなげられる。
Require comments when changing classification labels and keep history
Currently Box Shield does not allow the reason or history to be kept when changing.
We would like to see a comment input field added to the UI when making changes, and also made mandatory in the administrator settings.If it is a file, we would like to leave the comment entered in the comment (activity) field of the file so that the end user can check the history.
For folders, we would like to leave them as undeletable txt files, etc.Such a feature would allow all users above the…
1 vote -
Make setting a password for shared links mandatory.
Currently setting password for shared links is not mandatory. We would like to have the ability to set a global control that requires all public/open ('people with the link') links to be password-protected.
2 votes -
Automatically add a Group to all existing folders of an email address
Our department has been sharing one email address to manage Box folders. Now we want to use our individual emails and add our Group to the existing folders to maintain them. Currently we would have to select the folders individually and there are thousands so that is not realistic. It would be nice if there was a select all option for these folders to add our Group to.
1 vote -
About recycle bin settings for Enterprise
The Recycle Bin settings for Enterprise can be customized, but only users below the specified role can completely delete the contents in the Recycle Bin.
All users (including automation and policies)
None (content cannot be deleted by user or policy)
Policy only (users cannot delete content)
Admin only
Administrators and co-admins only
selected userItems that meet the retention policy are set to be permanently deleted.
However, there may be cases where a managed user accidentally uploads unnecessary files to Box. At that time, the administrator would like to delete the subject item completely.Therefore, in addition to the above, we would like to see an improvement to allow full deletion by "administrator or policy".
■日本語
件名：ごみ箱の完全に削除できるユーザの設定について
内容：
Enterprise用のごみ箱の設定をカスタマイズできるが、ごみ箱内のコンテンツを完全に削除できるのは指定したロールの以下ユーザーだけとなっている。すべてのユーザー (自動化とポリシーを含む)
なし (ユーザー、ポリシーによるコンテンツ削除不可)
ポリシーのみ (ユーザーによるコンテンツ削除不可)
管理者のみ
管理者および共同管理者のみ
選択したユーザーリテンションポリシーに合致したアイテムが完全削除されるよう設定をしてしようしています。
しかし、管理対象ユーザが誤ってBoxに不要なファイルをアップロードするケースが考えられる。
その際に管理者にて対象アイテムの完全削除を行いたいです。そのため、上記に加えて、”管理者もしくはポリシー”による完全削除ができるように改善してほしい。
The Recycle Bin settings for Enterprise can be customized, but only users below the specified role can completely delete the contents in the Recycle Bin.
All users (including automation and policies)
None (content cannot be deleted by user or policy)
Policy only (users cannot delete content)
Admin only
Administrators and co-admins only
selected userItems that meet the retention policy are set to be permanently deleted.
However, there may be cases where a managed user accidentally uploads unnecessary files to Box. At that time, the administrator would like to delete the subject item completely.Therefore, in addition to the above,…
20 votes -
Request：Unmanaged users Behaviour
There is a folder whose collaboration is allowed for only internal ( At folder settings, Restrict collaboratio within our company is checked )
One unmanaged user who uses company email domain but is associated with free box account is invited the folder, he/she is successfully invited. But auto expirtation for external collaborators ( which is set on enterprise settings) is also adopted to the user. This seems unnatrual and it is not reasonable.This is said by design, but could you consider improvng either 1 or 2 ?
1. if a folder is only allowed to collaborate internal, please restrict unmanaged users have been invited it.- If an unmanaed user is able to be invited in a folder only for internals, please handle the unamnaged user as same as managed users. don't treat like external users.
1 is best for us, for some particular reasons we can not use auto-rollin feature, and some part of users who use happened to make free box accounts by themseves.
There is a folder whose collaboration is allowed for only internal ( At folder settings, Restrict collaboratio within our company is checked )
One unmanaged user who uses company email domain but is associated with free box account is invited the folder, he/she is successfully invited. But auto expirtation for external collaborators ( which is set on enterprise settings) is also adopted to the user. This seems unnatrual and it is not reasonable.This is said by design, but could you consider improvng either 1 or 2 ?
1. if a folder is only allowed to collaborate internal, please restrict…2 votes -
Creating accounts containing double-byte characters should not be allowed, which violates RFC5322
Creating accounts containing double-byte characters should not be allowed, which violates RFC5322
(Reason)
Currently, it is possible to create a new account containing double-byte characters in an email address, but it cannot be activated because it cannot receive mail. However, as a result, accounts containing double-byte characters exist like zombies.In some external cloud services (Salesforce), this causes errors when retrieving the user list, but the root cause of this problem in the first place is that Box can create new accounts containing double-byte characters, which violates RFP5322 "3.4.1. Addr-Spec Specification," so I would like to see this specification changed.
(日本語)
RFC5322に違反する、全角文字を含むアカウント作成は許可すべきではない(理由)
現在、メールアドレスに全角文字を含む新規アカウントを作成することは可能であるが、メールを受信できないためアクティベートできない。しかし、その結果、全角文字を含むアカウントがゾンビのように存在してしまう。一部の外部クラウドサービス (Salesforce)では、これに起因してユーザー一覧取得時にエラーが起きるのだが、そもそもこの問題の根本的な原因は、Boxが2バイト文字を含む新しいアカウントを作成できることであり、RFP5322の"3.4.1. Addr-Spec Specification"に違反しているため、この仕様を変更してほしいです。
Creating accounts containing double-byte characters should not be allowed, which violates RFC5322
(Reason)
Currently, it is possible to create a new account containing double-byte characters in an email address, but it cannot be activated because it cannot receive mail. However, as a result, accounts containing double-byte characters exist like zombies.In some external cloud services (Salesforce), this causes errors when retrieving the user list, but the root cause of this problem in the first place is that Box can create new accounts containing double-byte characters, which violates RFP5322 "3.4.1. Addr-Spec Specification," so I would like to see this specification changed.
…
7 votes -
About Updating Assignee (s) Set to Workflow
Please improve so that when a user account is deleted by an administrator, it is also automatically deleted from the Assignee(s) in the workflow.
This is because a deleted user remaining in the workflow Assignee (s) can cause the workflow to stop and cause unintended actions.
Improvements are needed to ensure that the user's work is not interrupted.- in Japanese
管理者によってユーザーアカウントが削除された際、
連動してワークフローの担当者からも自動的に削除されるように改善をお願いいたします。BoxRelayのワークフローに設定される担当者に削除済のユーザーが残っていることでワークフローが停止されたり意図しない動作が発生する可能性があるためです。
ユーザーの業務が中断されないために改善が必要です。3 votes -
Box for Teams should disallow the use of the default folder.
Box for Teams should have the option to disallow using the default channel destination folder. This folder isn't connected to any person and can make it difficult to track data usage back to a department.
1 vote -
My client signed a file in Box Sign but it shows pending on my end. How do I get the signed copy?
I just want HELP FFS
1 vote -
Email Distribution List for Invoices
An option to forward invoices to multiple recipients in cases where various departments or vendors need copies of them.
1 vote -
Multiple Billing Contacts / Distribution option for invoices
Ability to add multiple billing contacts, or a distribution list, so invoices will be sent automatically to different personnel, departments, or vendors who need them such as a parent company, or compliance.
1 vote -
Search in safari broken
When searching within Safari the search is performed within the current folder with the option for Everywhere and Within <folder> appearing at the top.
In Safari when clicking on either Everywhere or Within this Folder the search disappears. As a result it is difficult to search everywhere, requiring a search to be done from the top parent folder.
This doesn't happen in Chrome, and seems to be a bug.
(For others that come across this, as a work around, pressing the down arrow then enter properly selects Everywhere without the search disappearing)
1 vote -
Increase scale of sort within a folder with page search query result limit
Limit the number of search results to improve results. Increase scale of items in folder that is sortable without error. Most interested in sort by file size, but should impact all types of sort.
2 votes -
Remove Logo on Expiring Embed Link
Hello, we would like the ability to remove the BOX logo when creating an expiring embed link while using the get file information. Just like the embed widget we would like the ability to disable the box logo when embedding an expiring embed link to an iFrame.
It would be a more seamless integration of BOX in the back ground as we are embedding these links into applications2 votes -
Make MPIP and Shield Classification Labels Bidirectional
This make require partnership with Microsoft, but it would be ideal if the MPIP integration was bidirectional. For example, if a file in Box doesn't have an MPIP label, but a Shield classification label is applied, the document would have an MPIP label applied based on the mapping table
14 votes -
A list of users who have sent "email to all" in a report.
The "Email All" function on the collaborator list screen on the folder screen allows you to check which user sent what message and when in the "User Activity Report", but it does not allow you to check which user the "Email All" was sent to.
I understand that "Email to all" cannot be sent to users with pending invitations or when there are more than 500 collaborators,
but when there are a large number of collaborators, it is difficult to know how many users are pending, and checking the "Collaboration Report" takes time.
In addition, there may be cases where emails cannot be sent due to reasons other than those mentioned above, so I would like a function to be implemented that would make it easier to identify users who have not been able to send emails by clearly indicating in the "User Activity Report" whether emails have been sent to that user.(日本語)
タイトル：「全員にメール」を送信したユーザー一覧をレポートで確認できるようにしたいフォルダ画面のコラボレータ一覧画面上にある「全員にメール」機能は「ユーザーアクティビティレポート」でどのユーザーがいつ、どのようなメッセージで送信したのか確認する事が可能ですが、どのユーザー宛に「全員へメール」が送信されたのか確認する事はできません。
「全員にメール」は招待が保留中のユーザーやコラボレータの人数が500名以上の場合に送信できない事を理解しているが、コラボレータ人数が多い場合、保留中のユーザーがどれぐらいいるのか把握が難しく、「コラボレーションレポート」で確認するのも時間がかかります。
また、上記要因以外に送信できない場合もあり、「ユーザーアクティビティレポート」でそのユーザーへ送信されたのか明記する事で、送信できていないユーザーを把握しやすくなる為、機能実装を希望します。The "Email All" function on the collaborator list screen on the folder screen allows you to check which user sent what message and when in the "User Activity Report", but it does not allow you to check which user the "Email All" was sent to.
I understand that "Email to all" cannot be sent to users with pending invitations or when there are more than 500 collaborators,
but when there are a large number of collaborators, it is difficult to know how many users are pending, and checking the "Collaboration Report" takes time.
In addition, there may be cases where…3 votes
- Don't see your idea?