10128 results found

1. Track the exact file version that was previewed or downloaded

   When a file has multiple versions, we need to know exactly which version was previewed or downloaded.

   Today, the Activity Report shows that a preview or download took place, but it does not identify the specific file version involved. This makes it difficult to confirm what content was viewed or shared, especially when investigating incidents, responding to audit requests, or checking whether the correct version was delivered to a customer or partner.

   Feature request: Please include the file version number, and ideally the version ID, in the event details for preview and download activities. This information would be especially valuable in the Activity Report, and would also be helpful in the Events API and other audit logs.

   Being able to trace who previewed or downloaded which version would improve auditability, accountability, and confidence in Box as a secure content platform.

   (Japanese)
   プレビュー・ダウンロードされたファイルバージョンを特定したい

   ファイルに複数のバージョンが存在する場合、どのバージョンがプレビューまたはダウンロードされたのかを正確に確認できるようにしてほしいです。

   現在のアクティビティレポートでは、プレビューやダウンロードが実行されたことは確認できますが、操作対象となったファイルのバージョンまでは分かりません。そのため、インシデント調査や監査対応、顧客・取引先へ正しいバージョンを共有できたかの確認において、実際に閲覧・取得された内容を特定することが困難です。

   要望: プレビューおよびダウンロードのイベント詳細に、ファイルのバージョン番号、可能であればバージョンIDも記録してほしいです。特にアクティビティレポートで確認できると助かります。また、Events APIやその他の監査ログでも取得できると、より幅広い運用に活用できます。

   「誰が」「どのファイルの」「どのバージョンを」プレビューまたはダウンロードしたのかを追跡できれば、監査性や説明責任が向上し、Boxをより安心して利用できるようになります。

   When a file has multiple versions, we need to know exactly which version was previewed or downloaded.

   Today, the Activity Report shows that a preview or download took place, but it does not identify the specific file version involved. This makes it difficult to confirm what content was viewed or shared, especially when investigating incidents, responding to audit requests, or checking whether the correct version was delivered to a customer or partner.

   Feature request: Please include the file version number, and ideally the version ID, in the event details for preview and download activities. This information would be especially valuable… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Admin Reports  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Add Company Branding to email notifications +

   The notification actions in Automate/Workflow are great, but I think there are a few opportunities to improve them:

   Allow company branding, such as logos and colours, to be included in notification emails.

   Option to include a direct link to the file that triggered the notification.

   Potentially allow notifications to be sent from a company email address through a Microsoft integration or similar connection.

   Branded notifications would increase engagement and make them feel more like part of our internal communications rather than system-generated messages.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Notifications  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Increase the Maximum Number of Actions per Box Automate Workflow

   {English}
   We would like to request an increase in the maximum number of actions that can be executed within a single Box Automate workflow.

   Currently, the limit is 200 actions per workflow execution. However, based on real customer business requirements, some workflows are reaching this limit and cannot be fully implemented within the current constraints.

   Increasing the limit to approximately 2,000 actions would address these use cases and enable customers to automate larger-scale business processes without requiring complex workarounds or workflow redesign.

   This request was submitted based on customer feedback.

   ====
   {Japanese}
   Box Automateワークフローで一度に実行できるアクション数の上限拡張を希望します。

   現在、1回のワークフロー実行で利用できるアクション数は200に制限されています。しかし、実際の顧客業務要件を考慮すると、この上限に達してしまい、実現できないフローが存在します。

   上限を2,000アクション程度まで拡張いただけると、このようなユースケースに対応でき、大規模な業務プロセスをワークアラウンドや複雑なフロー分割なしで実装できるようになります。

   本要望は顧客からのフィードバックに基づくものです。

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Box Automate  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Box Drive Cloud Files: Selecting the Cache Storage

   With the release of Box Drive Cloud Files, the specification for where the Box Drive cache is stored has been changed:
   Traditional Box Drive: C:\Users<USERNAME>\AppData\Local\Box\Box\cache
   Box Drive Cloud Files: Same folder as Box Drive
   In our company, we have changed the Box Drive mount location and are operating with a reduced capacity on that mounted drive. Due to the above specification change, upload errors caused by insufficient space are occurring.
   It is not realistically possible to re-image all corporate users’ PCs and change their storage capacities. A forced migration to Box Drive Cloud Files would therefore impact all users in our organization and could potentially lead to a decline in Box usage.
   We strongly request the addition of a feature in Box Drive Cloud Files that allows us to select the cache storage location on the C drive, as was possible with the previous specification.

   ---

   [Box Drive Cloud Files：キャッシュ保存先の選択]
   Box Drive Cloud Filesのリリースにより、Box Driveのキャッシュの保存先が仕様変更されました。
   ・従来のBox Drive：C:\Users<USERNAME>\AppData\Local\Box\Box\cache
   ・Box Drive Cloud Files：Box Driveと同じフォルダ内

   社内ではBox Driveのマウント先を変更しており、マウント先の容量を少なくして運用しています。
   上記の仕様変更の影響で、容量不足によるアップロードエラーが発生しています。
   社内のユーザーすべてのPCで再キッティングと容量変更をすることは現実的に不可能となり、
   Box Drive Cloud Filesへの強制移行は社内のすべてのユーザーに影響が出るため、Boxの利用率低下につながりかねません。

   従来の仕様と同じように、Box Drive Cloud Filesでもキャッシュの保存先をCドライブに選択できる機能の追加を強く要望します。

   With the release of Box Drive Cloud Files, the specification for where the Box Drive cache is stored has been changed:
   Traditional Box Drive: C:\Users<USERNAME>\AppData\Local\Box\Box\cache
   Box Drive Cloud Files: Same folder as Box Drive
   In our company, we have changed the Box Drive mount location and are operating with a reduced capacity on that mounted drive. Due to the above specification change, upload errors caused by insufficient space are occurring.
   It is not realistically possible to re-image all corporate users’ PCs and change their storage capacities. A forced migration to Box Drive Cloud Files would therefore impact all users in… more

   10 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Box Drive  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Compact / Dense File View – More Files and Search Results per Screen

   The current Box web interface uses far too much screen real estate per file/folder, particularly for organizations that work with very large project directories.

   At 100% browser zoom, both the List and Grid views display significantly fewer files than would reasonably fit on the screen. Large row heights, padding, thumbnails, and other UI elements make browsing folders or reviewing search results unnecessarily slow.

   Our users routinely work in project folders containing hundreds or thousands of engineering, survey, CAD, imagery, and PDF files. In that environment, filename density is much more important than large previews or generous spacing.

   We would like Box to provide a true Compact/Dense view that:

   • Significantly reduces row height and vertical padding in List view.
   • Provides a smaller-thumbnail option in Grid view.
   • Allows substantially more files/search results to be visible without scrolling.
   • Ideally lets users select display density: Comfortable / Compact / Dense.
   • Preserves filenames, modified date, size, and other useful metadata while reducing unused whitespace.

   A Windows Explorer-style compact view would be a good model. On a normal business monitor at 100% browser zoom, users should be able to see several times more results than the current Box interface permits.

   For organizations with very large file repositories, this is not simply cosmetic. The current layout materially affects navigation efficiency when users are browsing or searching through thousands of files.

   included a competitor's view...

   The current Box web interface uses far too much screen real estate per file/folder, particularly for organizations that work with very large project directories.

   At 100% browser zoom, both the List and Grid views display significantly fewer files than would reasonably fit on the screen. Large row heights, padding, thumbnails, and other UI elements make browsing folders or reviewing search results unnecessarily slow.

   Our users routinely work in project folders containing hundreds or thousands of engineering, survey, CAD, imagery, and PDF files. In that environment, filename density is much more important than large previews or generous spacing.

   We would like… more

   •  

   •  

   •  

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New UI  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Feature Request: Add Folder Tree View with Result Count Display in Box Search

   Currently, Box's search results page does not provide a folder tree view, making it impossible for users to visually understand how search results are distributed across the folder hierarchy. Users need the ability to exclude irrelevant department folders from their search results, but there is currently no way to get an overview of the folder structure within search results. We request the addition of a folder tree view in the search results page that displays the number of hits per folder and subfolder. This would allow users to drill down into the most relevant folders and refine their searches more effectively.

   Currently, Box's search results page does not provide a folder tree view, making it impossible for users to visually understand how search results are distributed across the folder hierarchy. Users need the ability to exclude irrelevant department folders from their search results, but there is currently no way to get an overview of the folder structure within search results. We request the addition of a folder tree view in the search results page that displays the number of hits per folder and subfolder. This would allow users to drill down into the most relevant folders and refine their searches more… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Search  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Expose flags or metadata indicating delays for Event Stream events

   We use information from the Event Stream to immediately detect actions that are prohibited by our internal rules. For this reason, knowing the timeliness and reliability of events is critical for our governance and security operations.

   Box has informed us that delays can occur before events appear in the Event Stream. We fully understand that in cases such as incidents or platform-level issues, it may take time for events to be reflected, and we are not requesting that all events always be strictly real-time.

   However, what we are missing today is visibility into:

   Which events were delayed
   How long each delayed event took to appear in the Event Stream
   Requested enhancement:

   Provide some form of delay indicator for each event when it is delivered via the Event Stream.
   For example, an additional field or flag that shows:
   Whether the event was delayed beyond the normal/expected latency
   The approximate delay duration or the time difference between when the event occurred and when it became available in the Event Stream
   Why this matters:

   We rely on Event Stream data to immediately detect and respond to prohibited actions according to our internal rules.
   Without any visibility into delays, we cannot distinguish between:
   A normal situation where no prohibited events occurred, and
   A situation where prohibited events did occur but are simply delayed in appearing in the Event Stream.
   This lack of visibility makes it difficult to design robust governance, monitoring, and alerting on top of the Event Stream.
   Reference:

   Events overview – Box Dev Docs
   https://developer.box.com/ja/guides/events/index
   We would greatly appreciate it if you could consider adding such delay indicators or flags for Event Stream events so that customers can better assess and manage the impact of any event delivery delays.

   We use information from the Event Stream to immediately detect actions that are prohibited by our internal rules. For this reason, knowing the timeliness and reliability of events is critical for our governance and security operations.

   Box has informed us that delays can occur before events appear in the Event Stream. We fully understand that in cases such as incidents or platform-level issues, it may take time for events to be reflected, and we are not requesting that all events always be strictly real-time.

   However, what we are missing today is visibility into:

   Which events were delayed
   How long each… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Collections View - Bring back view of all folders

   Bring back the folder view on collections. As someone who utilizes collections for many different purposes, the new view with folders showing at the very top and needing to expand is not helpful.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Collections  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. The ability to search by creator when searching workflows in the “Relay” section of the management console

   The administrator will check whether there are any problems with the workflow settings owned by each user, and if there are any problems, they may discuss with the user what needs to be corrected.
   Currently, workflows can be searched by name, but users cannot view a list of workflows they individually maintain, which lacks convenience.
   Searching by workflow creator improves work efficiency.

   管理者では各ユーザー毎の所有するワークフローの設定に問題がないか確認のうえ、問題があればユーザーと一緒に修正箇所を議論することがあります。
   現在はワークフローの名称で検索か可能となっていますが、各ユーザー毎に保持しているワークフロー一覧を出すことができず利便性に欠けます。
   ワークフローの作成者単位で検索できることで作業の効率化が上がります。

   19 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Admin Console  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Seamlessly Switch from Default Box AI Agent to Custom Agent Expanded Mode Without Losing Context.

    Please enable users to seamlessly switch to a Custom Agent with Expanded Mode when they reach the usage limit of the Default Box Agent.

    Today, users need to end their current Default Box Agent session and start a new session with the Custom Agent. As a result, they cannot retain the context from the previous conversation.

    Ideally, users should be able to continue in the same conversation and switch to a Custom Agent with Expanded Mode while preserving the existing context. We understand this may be technically challenging, but would greatly appreciate consideration from a user-experience perspective.

    Default Box Agentの利用上限に達した際、Custom Agent（Expanded Mode）へシームレスに切り替えられるようにしてほしいです。

    現状は、Default Box Agentのセッションを終了し、Custom Agentで新しいセッションを開始する必要があります。そのため、それまでの会話コンテキストを引き継ぐことができません。

    理想的には、同じ会話セッションを継続したまま、既存のコンテキストを保持してCustom Agent（Expanded Mode）へ切り替えられることを希望します。技術的に難易度が高い可能性は理解していますが、ユーザー体験の観点でぜひご検討をお願いします。

    Please enable users to seamlessly switch to a Custom Agent with Expanded Mode when they reach the usage limit of the Default Box Agent.

    Today, users need to end their current Default Box Agent session and start a new session with the Custom Agent. As a result, they cannot retain the context from the previous conversation.

    Ideally, users should be able to continue in the same conversation and switch to a Custom Agent with Expanded Mode while preserving the existing context. We understand this may be technically challenging, but would greatly appreciate consideration from a user-experience perspective.

    Default Box Agentの利用上限に達した際、Custom… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Box AI  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. AI-Powered Confirmation Before Adding Collaborators/Sending Links

    I’d like Box to add an AI-powered confirmation step when users invite collaborators to a file or folder or send shared links to other users. The AI would quickly scan the content, detect PII or sensitive information, understand the context, and check whether the invited collaborator seems appropriate (e.g., external domain, personal email, unrelated teammate). If something looks unusual, Box would display a confirmation prompt asking the user to verify the invitation. This would help prevent accidental oversharing and reduce security risks caused by human error, while still keeping the collaboration workflow smooth.

    17 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    researching  ·  0 comments  ·  Box AI  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. More flexible permission settings: control external Sign sending

    When Box Sign is enabled for a user, he/she can send sign requests, check the contents of requests shared with them, and view their inbox.
    However, there are users for whom I do not want to allow sending sign requests, but I do want them to be able to check their inbox.

    For example, our executives who frequently approve or sign documents in Box Sign but do not need to send signature requests by themselves.
    I believe it is a potential security risk to give users the authority to send signature requests even though they do not need it.

    Currently, Box Sign does not have a function to control external Sign sending. It would be great if we could have more granular control, such as allowing users to view the Sign inbox but not send requests.

    After signing, users can download and review the signed document and signature log via the sign completion email.
    But searching through the email inbox for them is inconvenient, so I would like to be able to complete everything within Box. So want to allow users to check the past signed document in Box via inbox of Box sign.

    I understand that with Shield access policies it is possible to restrict Box Sign request sending both internally and externally. However, since Box Sign may also be used for internal approval processes, I think making it completely impossible to send is too much.

    When Box Sign is enabled for a user, he/she can send sign requests, check the contents of requests shared with them, and view their inbox.
    However, there are users for whom I do not want to allow sending sign requests, but I do want them to be able to check their inbox.

    For example, our executives who frequently approve or sign documents in Box Sign but do not need to send signature requests by themselves.
    I believe it is a potential security risk to give users the authority to send signature requests even though they do not need it.

    Currently,… more

    31 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    not planned  ·  1 comment  ·  Box Sign  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Past password changes included in the report.

    Currently, it is possible to check the date and time of the last password change, but we have confirmed that past password change history is not included in the report.
    Being able to check how frequently passwords are changed will also help improve security.

    現在、最後にパスワード変更した日時を確認することは可能ですがこれまでに変更された実績がレポートに載らないことを確認してます。
    どれくらいの頻度で変更されているのか確認できることでセキュリティ向上にも繋がります。

    14 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin Reports  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Box for MIP

    Allow a single Microsoft Tenant to connect to more than one Box EID. We have two box EID's, one for "regular" content and the other for "FTI".

    13 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Partner Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Reference loop variables in a conditional branch within the loop in Box Automate workflow

    In a Box Automate workflow, when looping through files, we need to be able to run conditional checks on values/properties of the file within that loop.

    Potential use case: a user may want the workflow to ignore certain file types, or to only run Box AI Agent operations on certain files.

    Currently, many variables can be referenced within the "conditional split" element within a "loop" element, but not the loop variables themselves.

    •  

    •  

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Box Automate  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Allow admins to control which Prompt Library items are visible at the tenant level

    ▼What problem could Box solve for you?
    Box AI Home provides access to the Prompt Library, which helps users start with predefined prompts. However, in enterprise environments, not every prompt or prompt library is appropriate for every tenant, department, or business process.

    Administrators need the ability to control which prompt libraries are shown or hidden for their organization. Without this control, users may see prompts that are not relevant to their business, not aligned with internal policies, or not suitable for their industry-specific workflows.

    ▼Requested enhancement
    Please add tenant-level administrative controls for the Prompt Library, allowing admins to:

    1. View all prompt libraries available to the tenant.
    2. Choose which prompt libraries are displayed to users.
    3. Hide prompt libraries that are not relevant or not approved for organizational use.
    4. Optionally configure visibility by user group, department, or role.
    5. Provide a preview of the end-user Prompt Library experience from the admin console.

    ▼Business impact / use case
    In large enterprises, administrators are responsible for ensuring that AI features are adopted in a controlled and policy-aligned way. If the Prompt Library contains too many prompts, or prompts that do not match the organization’s use cases, users may become confused or may use prompts that do not fit internal guidelines.

    For example, an organization may want to display only prompts related to document summarization, policy review, and meeting preparation, while hiding prompts related to sales, marketing, legal, or other functions that are not relevant to the tenant’s rollout plan.

    This would also help organizations phase their Box AI adoption. Admins could start with a limited set of approved prompts, then gradually enable additional libraries as internal training and governance mature.

    ▼Expected outcome
    Admins can curate the Prompt Library experience for their tenant, improving usability, reducing confusion, and supporting safer Box AI adoption at scale.

    ---

    プロンプトライブラリの表示対象をテナント単位で管理者が制御できるようにしてほしい

    ▼Boxに解決してほしい課題
    Box AI Homeではプロンプトライブラリにアクセスでき、ユーザーはあらかじめ用意されたプロンプトを利用してAI活用を開始できます。一方で、エンタープライズ環境では、すべてのプロンプトライブラリがすべてのテナント、部門、業務プロセスに適しているとは限りません。

    管理者として、組織の方針や利用目的に合わせて、ユーザーに表示するプロンプトライブラリと表示しないプロンプトライブラリを選択できる必要があります。現状のままでは、業務に関係のないプロンプトや、社内ポリシーに沿わない可能性のあるプロンプトが一覧に表示され、ユーザーの混乱や誤った利用につながる懸念があります。

    ▼要望内容
    プロンプトライブラリについて、管理者がテナント単位で以下を設定できるようにしてほしいです。

    1. テナントで利用可能なプロンプトライブラリの一覧を管理者が確認できる。
    2. ユーザーに表示するプロンプトライブラリを選択できる。
    3. 組織で利用しない、または承認していないプロンプトライブラリを非表示にできる。
    4. 可能であれば、ユーザーグループ、部門、ロール単位で表示対象を制御できる。 5.管理コンソール上で、エンドユーザーにどのように表示されるかをプレビューできる。

    ▼業務上の効果・ユースケース
    大企業では、AI機能の展開において、管理者が社内ポリシーやガバナンスに沿った形で利用範囲を設計する必要があります。プロンプトライブラリに表示される項目が多すぎる場合や、自社の業務に合わないプロンプトが表示される場合、ユーザーが混乱したり、社内ルールに沿わない利用をしてしまう可能性があります。

    例えば、導入初期には「文書要約」「社内規程確認」「会議準備」に関するプロンプトのみを表示し、営業、マーケティング、法務など他部門向けのプロンプトは非表示にしたいケースがあります。

    また、Box AIの展開を段階的に進める際にも、管理者が承認済みのプロンプトライブラリのみを先に表示し、社内トレーニングや運用ルールが整った段階で追加のライブラリを有効化できると、より安全かつ計画的にAI活用を進められます。

    ▼期待される結果
    管理者がテナント単位でプロンプトライブラリの表示内容を管理できるようになり、ユーザーの利便性向上、混乱の抑制、Box AIの安全かつ統制された利用促進につながります。

    ▼What problem could Box solve for you?
    Box AI Home provides access to the Prompt Library, which helps users start with predefined prompts. However, in enterprise environments, not every prompt or prompt library is appropriate for every tenant, department, or business process.

    Administrators need the ability to control which prompt libraries are shown or hidden for their organization. Without this control, users may see prompts that are not relevant to their business, not aligned with internal policies, or not suitable for their industry-specific workflows.

    ▼Requested enhancement
    Please add tenant-level administrative controls for the Prompt Library, allowing admins to:

    1. View all… more
    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Box AI  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Enable branching from any point in a previous Box AI Home conversation

    ▼What problem could Box solve for you?
    Box AI Home provides session history and allows users to view and resume previous sessions. However, when users revisit a past conversation, they need the ability to branch from a specific point in the conversation and ask a new follow-up question without overwriting or altering the original conversation flow.

    Today, users may have long-running Box AI conversations involving multiple files, folders, or Hubs as sources. In many business scenarios, a user may want to go back to an earlier answer or question and explore a different direction from that exact point. For example, after asking Box AI to analyze a set of documents, the user may later realize that they want to ask a different follow-up question based on the third answer in the conversation rather than continuing from the latest answer.

    ▼Requested enhancement
    Please add a feature in Box AI Home that allows users to:

    1. Open a previous session from session history.
    2. Select any prior message or response in that conversation.
    3. Start a new question from that point.
    4. Automatically create a new branched conversation or new session, while preserving the original conversation unchanged.
    5. Clearly show that the new session was branched from the original session, ideally with a reference back to the source session and the selected branch point.

    ▼Business impact / use case
    This would improve productivity for users who conduct complex document analysis, legal review, policy review, research, proposal creation, or multi-document summarization using Box AI Home. Users would be able to explore multiple analytical paths without losing the original conversation context.

    This is especially important for enterprise use cases where AI conversations are used iteratively. Without branching, users must either continue from the latest point, manually recreate context, or start from scratch. This creates unnecessary friction and increases the risk of inconsistent analysis.

    ▼Expected outcome
    Users can safely explore different lines of questioning from earlier points in a Box AI Home conversation, while keeping the original session intact. This would make Box AI Home more useful as a persistent, auditable workspace for enterprise AI workflows.

    ---

    Box AI Homeの過去の会話において、任意の箇所から分岐して新しい質問を開始できるようにしてほしい

    ▼Boxに解決してほしい課題
    Box AI Homeでは、セッション履歴から以前のセッションを表示・再開できます。一方で、過去の会話を参照した際に、会話の最後から再開するだけでなく、会話の途中にある任意の質問・回答の時点に戻り、そこから新しい質問を行って別の会話として分岐できる機能が必要です。

    Box AI Homeでは、複数のファイル、フォルダ、Hubをソースとして、長い会話を通じて分析や要約を行うケースがあります。そのような場合、後から「この時点の回答を起点に別の観点で質問したい」「最新の回答からではなく、途中の回答から別ルートで検討したい」といったニーズが発生します。

    ▼要望内容
    Box AI Homeに以下の機能を追加してほしいです。

    1.セッション履歴から過去の会話を開く。
    2.過去会話内の任意の質問または回答を選択する。
    3.その時点を起点として新しい質問を開始する。
    4.元の会話を変更・上書きせず、新しい分岐会話または新しいセッションとして保存する。
    5.分岐元のセッションおよび分岐した位置が分かるように表示する。

    ▼業務上の効果・ユースケース
    この機能により、Box AI Homeを利用した複雑な文書分析、法務レビュー、規程確認、調査、提案書作成、複数文書の要約といった業務の生産性が向上します。

    現状では、過去の会話の途中から別の検討を行いたい場合でも、最新の会話末尾から続けるか、手動で文脈を再作成するか、新しいセッションを最初から作成する必要があります。これは作業効率を下げるだけでなく、分析の一貫性を損なう可能性があります。

    ▼期待される結果
    ユーザーは、元の会話を保持したまま、過去の任意の会話ポイントから安全に別の質問・分析ルートを開始できるようになります。これにより、Box AI HomeはエンタープライズAI業務における、より実用的で継続性のあるワークスペースになります。

    ▼What problem could Box solve for you?
    Box AI Home provides session history and allows users to view and resume previous sessions. However, when users revisit a past conversation, they need the ability to branch from a specific point in the conversation and ask a new follow-up question without overwriting or altering the original conversation flow.

    Today, users may have long-running Box AI conversations involving multiple files, folders, or Hubs as sources. In many business scenarios, a user may want to go back to an earlier answer or question and explore a different direction from that exact point. For example,… more

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Box AI  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. I want to set separate sharing restrictions for AI Home and Box Automate in [Additional collaboration configuration].

    Due to our policy of not allowing end users to invite collaborators, we have configured [Additional collaboration configuration] to [Restrict all collaboration and shared links] in order to deploy AI Home. While this setting is effective for deploying AI Home, it also restricts sharing in Box Automate, which prevents other users from running workflows whose trigger is set to [Manual Start].
    As a result, it is difficult for us to migrate from Relay to Automate. Although Automate offers more flexible and extensible functionality than Relay, this limitation prevents us from taking full advantage of it, which feels like a significant missed opportunity.
    It would be ideal if AI Home and Automate could be configured separately. This would allow us to maintain strict collaboration policies while still fully leveraging both AI Home and Box Automate.

    （日本語）
    エンドユーザーに招待させない運用のため、AI Homeの展開にあたり [追加のコラボレーション構成] を [すべてのコラボレーションと共有リンクを制限する] に設定しています。この設定はAI Homeの展開には有効ですが、一方でBox Automateの共有も制限してしまい、[手動で開始] のワークフローを他ユーザーが実行できません。
    その結果、RelayからAutomateへの移行が難しくなっています。Automateは、Relayよりも柔軟で拡張性の高い機能を備えているにもかかわらず、この制約によって十分に活用できないのは非常にもったいないと感じています。
    AI HomeとAutomateを別々に設定できるようになると理想的です。これにより、厳格なコラボレーションポリシーを維持したまま、AI HomeとBox Automateの両方を最大限活用できるようになります。

    Due to our policy of not allowing end users to invite collaborators, we have configured [Additional collaboration configuration] to [Restrict all collaboration and shared links] in order to deploy AI Home. While this setting is effective for deploying AI Home, it also restricts sharing in Box Automate, which prevents other users from running workflows whose trigger is set to [Manual Start].
    As a result, it is difficult for us to migrate from Relay to Automate. Although Automate offers more flexible and extensible functionality than Relay, this limitation prevents us from taking full advantage of it, which feels like a significant… more

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Admin Console  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Allow a table in Box Forms

    Allow a table in Box Forms to make entry easier for end users with copying and pasting

    7 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Box Forms & Doc Gen  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Ability to specify who will be notified when a password is changed.

    As part of security operational reviews, administrators may occasionally check whether passwords have been changed multiple times within the same day, when necessary.
    Currently, I believe password change notifications are sent to users with administrative privileges, including group administrators.
    For operational reasons, we would like group administrators not to receive these notifications, so we would like to be able to optionally configure the recipients of password change notifications.

    セキュリティ面の運用見直しの一環で、管理者で同日内に何度もパスワード変更していないか等を必要な時にチェック行うことがあります。
    現状、グループ管理者含めた管理者権限のあるユーザー宛にパスワード変更通知が届くと思います。
    運用上の理由からグループ管理者がこれらの通知を受け取らないようにしたいため、任意でパスワード変更通知先を設定できるようにしたいです。

    13 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Notifications  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating