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
21 results found
-
I want Japanese mark of a voiced sound in speech characters to be unified with NFC.
I want Japanese mark of a voiced sound in speech characters to be unified with NFC.
-Overview-
example: the 'ga' syllabary series in the Japanese alphabet
'ガ'is U+30AC on windows or unix/linux
-> NFC(Normalization Form Canonical Compression)
'ガ'is U+30AB U+3099U on mac OSX
-> NFD(Normalization Form Canonical Decompression)As you know, mac OSX use only NFD.
Windows use NFC usually, but NFD can be used at the same time.When trying to share BOX folder between Win and mac, Inconvenience occurs.
-problem-
First
In Windows explorer, NFC and NFD are displayed as the same character on the screen, so they are indistinguishable.The second
In Adobe InDesign, image files are managed as "link files", but file names are managed by NFC, so upload InDesign data created on mac OS to the shared BOX folder and download it on Windows. Cutting file link will occur.The third
Where NFC uses one character in UTF-8, NFD uses two characters in UTF-8.
The file "がぎぐげござじずぜぞだぢづでどばびぶべぼぱぴぷぺぽガギグゲゴザジズゼゾダヂヅデドバビブベボパピプペポヴ.txt" can be used on macOSX, but this file cannot be saved on the BOX server by Finder using BOX Drive.
Even if two characters are used, "xx.txt" uses only 106 characters.
And from Windows PC,
The file "がぎぐげござじずぜぞだぢづでどばびぶべぼぱぴぷぺぽガギグゲゴザジズゼゾダヂヅデドバビブベボパピプペポヴ.txt" (By NFC) there will be no problem with BOX Drive.
But, with macOS X / Box Drive, the inside of the BOX server is not displayed in the Finder.
"がぎぐげござじずぜぞだぢづでどばびぶべぼぱぴぷぺぽガギグゲゴザジズゼゾダヂヅデドバビブベボパピプペポヴ.txt"(By NFC) uses only 55 characters in NFC.
Are you having another problem?-Operation on mac OSX-
When writing to a FAT32 formatted USB memory device on mac OSX, write the file name using NFC.When uploading data to a shared folder using the cifs protocol on mac OSX, write the file name in NFC format.
When uploading data to a shared folder using the AFP protocol on mac OSX, write the file name in NFC format.
On mac OSX, write file name in NFD format only when writing data to HFS+ format HDD.
mac OSX does not accept any NFC on HFS+, and NFC automatically converts to NFD when downloading data from the BOX server.
-Proposal-
When writing data to the BOX server using BOX Drive for MacOS, please convert it to NFC instead of NFD and write the data.When uploading to the BOX server, no one will be troubled even if it is converted to NFC instead of NFD and saved. Inconvenience has occurred rather than being saved as NFD.
-Additional explanation-
mark of a voiced sound in speech characters is below.
がぎぐげご
ざじずぜぞ
だぢづでど
ばびぶべぼ
ぱぴぷぺぽ
ガギグゲゴ
ザジズゼゾ
ダヂヅデド
バビブベボ
パピプペポヴ
by NFC
がぎぐげご
ざじずぜぞ
だぢづでど
ばびぶべぼ
ぱぴぷぺぽ
ガギグゲゴ
ザジズゼゾ
ダヂヅデド
バビブベボ
パピプペポヴ
by NFD
I want Japanese mark of a voiced sound in speech characters to be unified with NFC.
-Overview-
example: the 'ga' syllabary series in the Japanese alphabet
'ガ'is U+30AC on windows or unix/linux
-> NFC(Normalization Form Canonical Compression)
'ガ'is U+30AB U+3099U on mac OSX
-> NFD(Normalization Form Canonical Decompression)As you know, mac OSX use only NFD.
Windows use NFC usually, but NFD can be used at the same time.When trying to share BOX folder between Win and mac, Inconvenience occurs.
-problem-
First
In Windows explorer, NFC and NFD are displayed as the same character on the screen, so they…3 votes
10097 results found
-
Box Automate: Local time zone support for date variables
We use Box Automate to move files into daily folders.
Because date/time variables are evaluated in UTC, workflows that run around local midnight (for example in JST) sometimes create folders with the previous day’s date.
We would appreciate it if you could add the following configuration options for the date/time variables used in folder and file names:(1) Ability to specify a time zone (e.g., Asia/Tokyo)
(2) Ability to perform date/time arithmetic (e.g., adding +9 hours to UTC)
＜Box Automate：日付変数のローカルタイムゾーン対応の要望＞
Box Automate でワークフロー実行日ごとにフォルダを作成・振り分けています。
現在は日付／時刻変数が UTC 基準で評価されるため、JST など UTC 以外の地域では深夜帯の実行時に前日の日付フォルダが作成されてしまいます。
フォルダ名・ファイル名用の日付／時刻変数について、以下を設定できる機能をご検討いただけますと幸いです。
(1) タイムゾーンの指定機能（例：Asia/Tokyo）
(2) 日時演算機能（例：UTC に +9 時間）11 votes -
Hub Collaboration Report
Box Hubs is a convenient feature that we use in our daily operations.
We would like to regularly perform checks to make sure there are no users who have been unintentionally invited to our Hubs.Currently, we can check this through the UI, such as the Admin Console or the [Share] screen of each relevant Hub, but there is no way to obtain a list.
If there were a function similar to the Collaboration Report that could export a report of all users invited to each Hub, our work would be much smoother.
Hubに意図せず招待されたユーザーがいないか定期的に棚卸作業を実施したいです。
現在は、管理コンソールや対象のHub画面の[共有]などUI上から確認できますが、一覧を取得する方法がありません。
コラボレーションレポートのように各Hubに招待されているユーザーをレポートで出力できる機能を実装してほしいです。37 votes -
Box Sign: Stop Sign from creating managed (paid) accounts for signers
Problem statement
When someone without a Box account signs a Box Sign request, Box creates an account for them to hold their copy of the signed document and signing log. If their email matches your verified domain and you have auto-enrollment or SSO with auto-provisioning turned on, that account is converted into a paid managed user in your enterprise.Current workarounds:
1. Manually delete the created accounts
2. Turn off auto-provisioning while keeping auto-enrollment and SSO on
3. Turn off auto-enrollment entirely (with auto-provisioning and SSO off)Requested enhancements
Exempt Box Sign account creation from Auto Enrollment.This would be particularly valuable for organizations that send Sign requests to large numbers of their own people who don't otherwise need a Box license
Problem statement
When someone without a Box account signs a Box Sign request, Box creates an account for them to hold their copy of the signed document and signing log. If their email matches your verified domain and you have auto-enrollment or SSO with auto-provisioning turned on, that account is converted into a paid managed user in your enterprise.Current workarounds:
1. Manually delete the created accounts
2. Turn off auto-provisioning while keeping auto-enrollment and SSO on
3. Turn off auto-enrollment entirely (with auto-provisioning and SSO off)Requested enhancements
Exempt Box Sign account creation from Auto Enrollment.This would be…
12 votes -
Increase of the upper limit on the number of metadata templates that can be created and permission management for metadata templates
Currently, our company has a wide variety of unstructured data, and we would like to make use of metadata templates. However, there are significant differences in the templates that each on-site team wants to use. At present, metadata templates can only be created up to 500 per tenant, which leads to competition over templates. We would like to be able to create an almost unlimited number of metadata templates.
In addition, once a metadata template is created, it becomes viewable across the entire tenant, which feels inconsistent with Box’s underlying philosophy of content-level permission management. We would like metadata templates as well to be controllable by permissions, from viewing to actual usage.ーー日本語ーー
現在、当社では様々な非構造データがあるため、メタデータテンプレートを活用したいと考えているが、各現場で利用したいテンプレートにかなりの差異がある。
しかしメタデータテンプレートは現在テナント上で500個までしか作成が出来ないため、テンプレートの取り合いが発生してしまう。
無制限に近い数のメタデータテンプレートが作成できるようになってほしい。また、現在はメタデータテンプレートを作成するとテナント内すべてで閲覧ができるようになってしまうが、これはBoxの各コンテンツの権限管理の思想と乖離しているように感じます。
メタデータテンプレートも閲覧から利用の範囲が権限でコントロールできるようになってほしい。Currently, our company has a wide variety of unstructured data, and we would like to make use of metadata templates. However, there are significant differences in the templates that each on-site team wants to use. At present, metadata templates can only be created up to 500 per tenant, which leads to competition over templates. We would like to be able to create an almost unlimited number of metadata templates.
In addition, once a metadata template is created, it becomes viewable across the entire tenant, which feels inconsistent with Box’s underlying philosophy of content-level permission management. We would like metadata templates…18 votes -
I want to use the form trigger variables even outside of the [Request Signature] action.
Currently, when [Form Submitted] is used as the trigger in Box Automate, the [Request Signature] action can use variables from the form trigger. However, these variables cannot be used in other actions, such as [Task Action].
If form-trigger variables could be used in other actions as well, the range of automations that can be achieved with Box Automate would expand further, making it much more convenient. We kindly ask you to consider this enhancement.（日本語）
現在、Box Automateで [フォームを送信] をトリガーとした場合、[署名をリクエスト] アクションではフォームトリガーの変数を利用できます。しかし、[タスクアクション] など、その他のアクションではこれらの変数を利用できません。
他のアクションでもフォームトリガーの変数を利用できるようになると、Box Automateで実現できる自動化の幅がさらに広がり、大変便利になると考えています。ご検討をお願いいたします。8 votes -
Displaying Tag Suggestions to Collaborators
When performing a tag-based search, content owners see tag suggestions automatically populated in the search view as they type the first few characters.
However, users who are not the content owner do not see any suggested terms, so they must already know the exact tags that have been registered.
Because there are many types of tags applied to content across the organization, it is difficult for users to always know all tags accurately.
Even for content they do not own, we would like users to see suggested tag terms during tag search for any tags that are used on content they are collaborating on.
(In Japanese)
タグベースの検索を行う際、コンテンツ所有者は、検索画面で最初の数文字を入力すると、自動的にタグ候補が表示されます。
しかし、コンテンツ所有者ではないユーザーには候補が表示されないため、登録されている正確なタグをあらかじめ把握しておく必要があります。
組織全体でコンテンツに適用されるタグの種類は多岐にわたるため、ユーザーが常にすべてのタグを正確に把握することは困難です。所有していないコンテンツであっても、ユーザーが権限を持つコンテンツで使用されているタグについては、タグ検索時に候補タグが表示されるようにしてほしい
When performing a tag-based search, content owners see tag suggestions automatically populated in the search view as they type the first few characters.
However, users who are not the content owner do not see any suggested terms, so they must already know the exact tags that have been registered.
Because there are many types of tags applied to content across the organization, it is difficult for users to always know all tags accurately.
Even for content they do not own, we would like users to see suggested tag terms during tag search for any tags that are used on content…
21 votes -
Add the "specify when started" option for manual start task automations
In Box Relay, for a manual start relay that assigns a task, you had the option to specify the assignees at the time of the relay being started. This option doesn't appear to be possible in Box Automate. Our users are asking that this be added back in. Thanks
6 votes -
Display folder sizes when sorting by size and support sorting by file count
In Box Web, content can be sorted by “Size,” but the Size column for folders displays the number of files rather than the folder’s storage size.
As a result, even when the contents are sorted by storage size, the screen may display file counts such as “1,000,” “20,” and “600.” This can lead users to mistakenly believe that the contents have not been sorted correctly.
We would like to request the following improvements:・Display the folder’s storage size alongside the file count in the Size column
・Allow users to sort folders by file count in addition to storage sizeThese improvements would make it easier to select targets and estimate processing time for LFO operations, migration, data review, and capacity management. They would also help users assess data volume and potential impact more accurately during security incidents, improving operational efficiency and security governance.
＝＝＝
サイズ順ソート時の容量表示と、ファイル数順ソートへの対応
Box Webではコンテンツを「サイズ」順にソートできますが、フォルダのサイズ列には容量ではなくファイル数が表示されます。
そのため、容量順にソートしているにもかかわらず、画面上では「1,000」「20」「600」のようにファイル数が表示され、正しくソートされていないと誤解してしまうことがあります。以下の改善を希望します。
・フォルダのサイズ列に、ファイル数だけでなく容量も併記する
・サイズ順に加えて、ファイル数順でもソートできるようにする本改善により、LFO処理、移行、棚卸し、容量管理における対象選定や処理時間の見積もりが容易になります。また、インシデント発生時のデータ量・影響範囲の把握にも役立ち、運用効率とセキュリティガバナンスの向上につながります。
In Box Web, content can be sorted by “Size,” but the Size column for folders displays the number of files rather than the folder’s storage size.
As a result, even when the contents are sorted by storage size, the screen may display file counts such as “1,000,” “20,” and “600.” This can lead users to mistakenly believe that the contents have not been sorted correctly.
We would like to request the following improvements:・Display the folder’s storage size alongside the file count in the Size column
・Allow users to sort folders by file count in addition to storage sizeThese…
7 votes -
Saved Prompts Cannot Be Used Mid-Session
Currently, saved prompts in Box AI Home can only be selected at the beginning of a session. Users cannot introduce a saved prompt during an active conversation, preventing them from applying it to the existing session context.
8 votes -
I’d like the workflow error messages to include specific details about what the problem is.
Now that BoxAutomate has been released, I’m really excited about all the new possibilities it will unlock inside Box.
However, with the current specifications, when an error occurs in a workflow, a message is displayed, but it doesn’t tell us what exactly went wrong.
With things the way they are, it’s impossible for us to fix the workflow on our own. It’s like being told, “Something’s broken… somewhere… good luck!”
To enable users to fix errors by themselves, we’d like the error messages to clearly specify the detailed points where the problem occursワークフローでエラーが発生した場合、メッセージが表示されるが、具体的にどこが問題なのかが分からないです。
これではワークフローを自分たちで修正することもできません。
ユーザーが自分でエラーを直せるように、エラーメッセージには詳細なポイントを明記してほしいと考えています。13 votes -
Box Sign for Autodesk Integration
Build a productized, out-of-the-box Box Sign integration for Autodesk. This will allow customers to replace current eSignature integrations with Box Sign without bespoke iPaaS, custom scripting, or one-off engineering, preserving user experience and automation while reducing costs.
Request to Build a Box Sign Autodesk connector that:
- Creates Box Sign envelopes via API from Autodesk-generated documents.
- Subscribes to Box Sign webhooks for lifecycle events and updates Autodesk objects.
- Transfers signed artifacts into Autodesk commitment attachments via Autodesk APIs.
- Ensures attachments continue to sync to Box files.
- Provide a template-mapping UI in Autodesk and comprehensive admin documentation.
Aim to embed logic in the connector so customers avoid custom codeBuild a productized, out-of-the-box Box Sign integration for Autodesk. This will allow customers to replace current eSignature integrations with Box Sign without bespoke iPaaS, custom scripting, or one-off engineering, preserving user experience and automation while reducing costs.
Request to Build a Box Sign Autodesk connector that:
- Creates Box Sign envelopes via API from Autodesk-generated documents.
- Subscribes to Box Sign webhooks for lifecycle events and updates Autodesk objects.
- Transfers signed artifacts into Autodesk commitment attachments via Autodesk APIs.
- Ensures attachments continue to sync to Box files.
- Provide a template-mapping UI in Autodesk and comprehensive admin documentation.…24 votes -
Enable Microsoft 365 Copilot in Excel Online for Excel files stored in Box
[English]
We would like Microsoft 365 Copilot in Excel to be available when an Excel file stored in Box is opened and edited with Excel Online from the Box web application.
Currently, users can open Excel files stored in Box using Excel Online and edit them collaboratively. However, the native Copilot functionality in Excel is not available or enabled for these files because the files are stored in Box rather than in OneDrive or SharePoint.
This results in an inconsistent user experience:
- Excel files stored in OneDrive or SharePoint can use the native Copilot features in Excel.
- The same Excel files stored in Box can be opened and edited in Excel Online, but the native Copilot features are unavailable.
- Users must copy or move files to OneDrive or SharePoint if they want to use Copilot in Excel.
- This creates duplicate files, complicates version management, and conflicts with organizations that use Box as their primary content management platform.
The Box Copilot Connector and Box AI Agent in Copilot provide useful capabilities for searching, summarizing, and querying Box content. However, these features are different from using the native Copilot experience directly within an Excel workbook, such as generating formulas, analyzing tables, identifying trends, creating charts, and editing workbook content.
We request that Box work with Microsoft to enable the native Microsoft 365 Copilot experience in Excel Online when users open Excel files stored in Box.
Expected experience:
- A user opens an Excel file stored in Box.
- The user selects “Open with Microsoft Excel Online.”
- Excel Online recognizes the user’s Microsoft 365 Copilot license.
- The Copilot button and Copilot features are available in the workbook.
- Changes made by Copilot are saved directly back to the file in Box without requiring the file to be copied to OneDrive or SharePoint.
This enhancement would allow organizations to maintain Box as their system of record while taking advantage of Microsoft 365 Copilot in Excel. It would also prevent duplicate content and significantly improve productivity for customers using both Box and Microsoft 365.
[日本語]
BoxのWebアプリケーションから、Box上に保存されているExcelファイルをExcel Onlineで開いて編集した場合でも、Excel内蔵のMicrosoft 365 Copilotを利用できるようにしてほしいです。
現在、Boxに保存されているExcelファイルをExcel Onlineで開き、共同編集することはできます。しかし、ファイルの保存先がOneDriveまたはSharePointではなくBoxであるため、Excel内蔵のCopilot機能が表示されない、または有効になりません。
このため、以下のような利用体験の差が発生しています。
・OneDriveまたはSharePointに保存したExcelファイルでは、Excel内蔵のCopilotを利用できる
・同じExcelファイルをBoxに保存した場合、Excel Onlineで編集することはできるが、Excel内蔵のCopilotを利用できない
・Copilotを利用するためには、ファイルをOneDriveまたはSharePointへコピーまたは移動する必要がある
・その結果、ファイルの重複、バージョン管理の複雑化、Boxを正式なコンテンツ管理基盤として利用する組織の運用方針との不整合が発生するBox Copilot ConnectorやCopilot向けBox AIエージェントにより、Boxコンテンツの検索、要約、質問などができることは理解しています。しかし、これらはExcelブック内で数式の生成、表の分析、傾向の抽出、グラフの作成、セルやシートの直接編集などを行う、Excel内蔵のCopilotとは異なる機能です。
Boxに保存されているExcelファイルをExcel Onlineで開いた場合でも、Excel内蔵のMicrosoft 365 Copilotを利用できるよう、Microsoftとの連携強化を要望します。
期待する利用方法は以下のとおりです。
- ユーザーがBoxに保存されているExcelファイルを開く
- 「Microsoft Excel Onlineで開く」を選択する
- Excel OnlineがユーザーのMicrosoft 365 Copilotライセンスを認識する
- Excelブック内でCopilotボタンおよびCopilot機能を利用できる
- Copilotによる編集結果が、OneDriveやSharePointへファイルをコピーすることなく、Box上の元ファイルへ直接保存される
この機能が実現すれば、Boxを正式なコンテンツ管理基盤として維持しながら、Microsoft 365 CopilotのExcel機能を活用できます。また、ファイルの重複を防止し、BoxとMicrosoft 365を併用している企業の生産性を大きく向上させることができます。
[English]
We would like Microsoft 365 Copilot in Excel to be available when an Excel file stored in Box is opened and edited with Excel Online from the Box web application.
Currently, users can open Excel files stored in Box using Excel Online and edit them collaboratively. However, the native Copilot functionality in Excel is not available or enabled for these files because the files are stored in Box rather than in OneDrive or SharePoint.
This results in an inconsistent user experience:
- Excel files stored in OneDrive or SharePoint can use the native Copilot features in Excel.
- The same Excel…
8 votes -
Add support in Box UI Elements for users to rename files before upload is completed in mobile/embedded experience
This enhancement would improve document capture workflows where meaningful filenames are needed at the point of upload for easier identification, retrieval, and downstream usability. Today, the lack of rename-during-upload support creates friction for mobile use cases, reduces efficiency when many similar files are uploaded, and can force teams to rely on custom upload logic instead of standard Box UI Elements.
Requested enhancement:
• Allow users to edit filenames before upload commit
• Ensure the experience works well on mobile form factors
• Preserve the user-defined filename in Box after upload
• Optionally support configurable naming rules or validations for admins and developersBusiness value:
• Improves usability in mobile document capture workflows
• Increases searchability and operational efficiency
• Reduces dependence on custom integrations
• Strengthens adoption of Box-native embedded experiencesThis enhancement would improve document capture workflows where meaningful filenames are needed at the point of upload for easier identification, retrieval, and downstream usability. Today, the lack of rename-during-upload support creates friction for mobile use cases, reduces efficiency when many similar files are uploaded, and can force teams to rely on custom upload logic instead of standard Box UI Elements.
Requested enhancement:
• Allow users to edit filenames before upload commit
• Ensure the experience works well on mobile form factors
• Preserve the user-defined filename in Box after upload
• Optionally support configurable naming rules or validations for admins and…12 votes -
Add Ability to Duplicate an Existing Box Form
Please add a feature that allows users to duplicate an existing Box Form, including all fields, structure, metadata mappings, and settings. Users should be able to clone a form, rename it, and make edits without rebuilding from scratch.
Why This Matters
Saves significant time when creating similar forms across departments, programs, or agencies.
Reduces errors by ensuring consistent fields, metadata, and logic across related forms.
Enables scalable templates, especially for public sector workflows like procurement, HR, inspections, grants, benefits, and compliance.
Accelerates PS SE and customer builds, allowing faster demos, labs, and solution rollouts.
Supports versioning needs, since agencies routinely update forms as policies and regulations change.
Impact
Faster solution deployment, higher form adoption, reduced build errors, and more repeatable patterns for enterprise and public sector customers.
Please add a feature that allows users to duplicate an existing Box Form, including all fields, structure, metadata mappings, and settings. Users should be able to clone a form, rename it, and make edits without rebuilding from scratch.
Why This Matters
Saves significant time when creating similar forms across departments, programs, or agencies.
Reduces errors by ensuring consistent fields, metadata, and logic across related forms.
Enables scalable templates, especially for public sector workflows like procurement, HR, inspections, grants, benefits, and compliance.
Accelerates PS SE and customer builds, allowing faster demos, labs, and solution rollouts.
Supports versioning needs, since agencies routinely…
37 votes -
Request for AI Unit Usage Limits by User and Group
We would like the ability to control AI Unit consumption at both the user and group levels.
Currently, AI Unit usage can be difficult to manage across different departments and user types. We would like administrators to be able to:Set AI Unit usage limits for individual users
Set AI Unit usage limits for groups or departments
Receive alerts when usage approaches configured limits
Prevent excessive AI Unit consumption and improve cost controlThis enhancement would help organizations govern AI usage more effectively and allocate resources according to business needs.
9 votes -
Admin-controlled AI model governance
Public sector and other regulated customers need stronger admin governance over Box AI model behavior. While admins can select a primary AI model today, they cannot control what happens if that model becomes unavailable. For FedRAMP, CJIS, and procurement-constrained environments, automatic failover to an unspecified model introduces compliance and risk concerns. Box should allow admins to select a primary (default) AI model, restrict usage to an approved model list, and explicitly define fallback behavior if the primary model goes down: either fail over to an admin-approved backup model or automatically disable Box AI. That the list of AI Providers in the AI settings tab MUST include all families of LLMs This ensures deterministic, compliant AI behavior aligned to agency authorization, vendor approval, and risk management requirements, while preventing exposure to unapproved models.
Public sector and other regulated customers need stronger admin governance over Box AI model behavior. While admins can select a primary AI model today, they cannot control what happens if that model becomes unavailable. For FedRAMP, CJIS, and procurement-constrained environments, automatic failover to an unspecified model introduces compliance and risk concerns. Box should allow admins to select a primary (default) AI model, restrict usage to an approved model list, and explicitly define fallback behavior if the primary model goes down: either fail over to an admin-approved backup model or automatically disable Box AI. That the list of AI Providers in…
30 votes -
Implementing a "pause" or "delay" feature in Box Automate outcomes
Currently, all outcomes in Box Automate happen sequentially, but sometimes there's a need for a certain amount of time to pass before the outcome needs to happen.
Creating flexible timeframes such as "after [#] [days/weeks/months]" would be helpful.
5 votes -
In the "Folders and Files" report, I want to get the number of contents for each folder.
When copying or moving content, the process tends to become unstable or more prone to errors as the number of contents in the target folder increases. Therefore, as a countermeasure, there are cases where content is divided into smaller parts and copied/moved multiple times. However, currently, the number of contents per folder, which serves as a basis for this judgment, cannot be obtained from the report.
It would be very helpful if the "Folders and Files" report could also retrieve the number of contents in each folder.
This allows you to identify folders with a large number of items in advance, enabling you to plan copying/moving more safely. It is also believed to contribute to large-scale content migration and improved stability of daily operations.
（日本語）
コンテンツのコピーや移動を行う際、対象フォルダ内のコンテンツ数が多いほど、処理が不安定になったりエラーになりやすいです。そのため、対策としてコンテンツを小分けにして、複数回に分けてコピー／移動したいケースがあります。しかし現在は、その判断材料となるフォルダごとのコンテンツ数を、レポートから取得できません。
フォルダとファイルレポートで、各フォルダのコンテンツ数も取得できるととても助かります。
これにより、事前に件数の多いフォルダを把握して、より安全にコピー／移動の計画を立てられるようになります。大規模なコンテンツ移行や日常運用の安定性向上にもつながると考えます。When copying or moving content, the process tends to become unstable or more prone to errors as the number of contents in the target folder increases. Therefore, as a countermeasure, there are cases where content is divided into smaller parts and copied/moved multiple times. However, currently, the number of contents per folder, which serves as a basis for this judgment, cannot be obtained from the report.
It would be very helpful if the "Folders and Files" report could also retrieve the number of contents in each folder.
This allows you to identify folders with a large number of items in…8 votes -
Automate Failure Notifications
Allow Admins/Co-Admins to set up automatic alerting or notifications if an Automate workflow has failed at any step. Currently, the only way to check this is to go to the Tracking page. Tracking needs notification events that can be enabled for better monitoring.
4 votes -
Customized email contact for “Disabled by Administrator” error in Microsoft 365 Copilot- MCP
Request for a way to change the email address listed in the “Disabled by Administrator” message for Box Copilot connectors. Currently, the error flow directs users to the primary admin account in the tenant and we’d like to direct them to the general support email address. There is the option to configure alternative contact info displayed on login or when a user hits the help button, but that doesn't appear to extend in the general UI.
4 votes
- Don't see your idea?