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 ~
9665 results found
-
hubs thumbnails
When viewing an anonymous Hub, and the user is not authenticated, thumbnails of the files are not displayed, you only see an icon. It would be much more visually appealing if the thumbnails were shown for anonymous users.
1 vote -
Box AI
box AI for meeting transcripts
Will Box AI have capability to capture speech and write into Box Notes? We use Box Notes for all our internal meetings so having Box AI in Box Notes is great but could it also capture the meeting discussion and create a full transcript of the meeting? Maybe via Box Mobile or using Zoom integration with Box? Thinking similar to GONG call recordings.
3 votes -
set a password for a folder
Because Box's access rights are waterfall, access rights set at a higher level cannot be removed from lower levels.
Instead of removing access rights, I want to set a password for the folder to limit who can access it.1 vote -
Provide Box plugin for Microsoft 365 Copilot
Copilot plug-ins have the advantage that data can be handled in real time, and there are no limit to the number of items, etc.
In addition to the Graph Connector, the Box plug-in for Copilot integration is also required.
Appendix.
https://learn.microsoft.com/ja-jp/microsoft-365-copilot/extensibility/
8 votes -
IP Whitelisting
Please find our use case below for your better understanding and let us know how Box can support our requirements.
We are working with multiple clients, and our primary focus is data handling, especially PII data. Currently, we have a centralized storage system (File Server) to store client data files and folders, which are accessible by both internal users and clients, based on the access permissions we provide.
We are now planning to create Box accounts for each client, store the data there, and grant access to files/folders for our internal users as external collaborators. In this setup, the Box console should only be accessible through whitelisted IP addresses for our internal users (external collaborators). Internal users should only be able to access client files/folders from their Box account when connected to our domain network.
After conducting a POC, we found that we cannot implement IP address whitelisting for external collaborators, nor can we control external collaborators' Box interfaces from the client Admin console. Many of the security policies are unavailable for external users.
Essentially, clients will share files with us, and our internal users will simply view, edit, and share the files without being able to download them. There is no need to integrate with any third-party applications.
Please review the above and let us know if this requirement is feasible with Box. Alternatively, if there are other options within Box that could support our needs, we would appreciate your guidance.
Please find our use case below for your better understanding and let us know how Box can support our requirements.
We are working with multiple clients, and our primary focus is data handling, especially PII data. Currently, we have a centralized storage system (File Server) to store client data files and folders, which are accessible by both internal users and clients, based on the access permissions we provide.
We are now planning to create Box accounts for each client, store the data there, and grant access to files/folders for our internal users as external collaborators. In this setup, the Box…
1 vote -
Allow user to upload file but prevent folder creation
Currently when using content explorer for box. we create ollaboration for user and even downscope the token to limit access. but there is no way where we can allow user to upload file only and prevent folder creation at same location.
1 vote -
Box shuttle client app for MacBooks
Box shuttle client app for MacBooks - needed badly for exited employees on Macs.
2 votes -
the ability to see only files and folders names which managed users were invited
Currently, co-administrators who have been granted permission to [view the user's content] can see which managed users have been invited to which folders and what content is within those folders. Additionally, they can preview the files.
Since the helpdesk operations are outsourced, we would like the external staff to be able to confirm only the folder names and file names from the Content Manager, without being able to view or edit the contents of the files.
Please enable the ability to grant co-administrators the permission to reference only the folder and file names, while restricting access to the contents inside.
2 votes -
Metadata overlay as header / footer or document watermark
Legacy ECM technology can overlay metadata attributes directly on versions of the document or when the document is printed. Metadata overlays are used for audit trails, SOPs, and other "point-in-time" compliance & records management use cases. In order to provide capabilities on par with legacy ECM technology, Box should consider additional advanced metadata features, such as printing or watermarking certain file types with attributes.
5 votes -
more colours in canvas
I would like to have more choices of colours when using shapes.
Ideally the amount of choices in Microsoft Word and Powerpoint5 votes -
Content Insights reports cannot be output if there are restrictions on content creation.
(Japanese follows English)
There is a function to export Content Insights access statistics, but if you restrict content creation and prohibit the creation of first-level folders, you will not be able to export it.
Currently, there are many cases in which system administrators are required to respond to requests, which places a heavy burden on both administrators and users, and hinders the use of content insights.
Please enable output even in tenants that have restrictions on content creation, such as specifying the report output destination or outputting to a local file.
コンテンツ作成の制限が入っているとコンテンツインサイトのレポートが出力出来ない
コンテンツインサイトのアクセス統計情報をエクスポートという機能がありますが、コンテンツ作成の制限をして第一レベルのフォルダの作成を禁止している場合は出力ができません。
現状だとシステム管理者に依頼を受けて対応するケースが多く、管理者、利用者とも負荷が大きく、コンテンツインサイトの活用の阻害となっています。
レポートの出力先を指定する、ローカルにファイル出力するなどコンテンツ作成の制限が入っているテナントでも出力できるようにしてください。28 votes -
Ability to tie one BoxEID to a specific microsoft365 tenant.
When I add and activate Microsoft Power Automate to the Box app, it can be linked to multiple microsoft365 tenants.
We would like BoxEID to be linked to a microsoft365 tenant and only be available in specific environments.In Japanese:
Microsoft Power AutomateをBoxのアプリに追加して有効化すると、
複数のmicrosoft365テナントと連携ができてしまいます。
BoxEIDとmicrosoft365テナントを結び付けて、特定環境でのみ利用ができるようにしてほしいです。22 votes -
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 votesThe Box Shield Product team is researching the ask.
-
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…
20 votes
- Don't see your idea?