10094 results found

1. Make folder retention policies non-removable (or always visible) to Editors

   Today, Editors can remove the visible retention policy from a file or folder’s details panel, even though the underlying non-modifiable retention policy remains active in the background. This means that after an Editor removes the visible policy, there is no indication in the UI that retention still applies, which makes it appear as though the content is not under retention at all.

   This behavior causes confusion for end users and admins, and makes it harder to support clear records management and compliance because enforced retention is not transparently visible in the interface.

   Feature request
   Please provide one or more of the following options:
   -An option so Editors cannot remove the visible retention policy from files and folders (only Admins or users with Retention permissions can).
   -If Editors can “remove” it, the UI should still clearly indicate that the item is under an enterprise retention policy (for example, a non-removable badge, icon, or message in the details panel).
   -An admin-level configuration that controls whether retention policies are removable or always displayed when they apply.

   Implementing this would make retention behavior more transparent, reduce user confusion, and better support compliance needs.

   Thank you.

   Today, Editors can remove the visible retention policy from a file or folder’s details panel, even though the underlying non-modifiable retention policy remains active in the background. This means that after an Editor removes the visible policy, there is no indication in the UI that retention still applies, which makes it appear as though the content is not under retention at all.

   This behavior causes confusion for end users and admins, and makes it harder to support clear records management and compliance because enforced retention is not transparently visible in the interface.

   Feature request
   Please provide one or more of… 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  ·  Metadata  ·  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. capture history should be optional

   The Capture History should be optional to toggle on or off.
   We have a folder that relays the file to a secure location. We have onboarding iPads that we use to have people fill out their forms that contains sensitive information, and then they place that file in that folder. The onboarding team just realized that a copy of that file and any images/pdf's are being stored in a different folder.

   We want to keep our information secure, and this automatic feature isn't beneficial for our use of Box. We don't want to have to manually delete each copy.

   1 vote

   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  ·  Security  ·  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 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… more

   18 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  ·  Metadata  ·  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. In my Salesforce Org we have Box managed package installed, some apex classes as part of package are using account and contact name fields

   n my Salesforce Org ha we have Box managed package installed, some apex classes as part of package BoxAILWCControllerEnhancedTests, BoxFileService are using account and contact name fields in soql queries with like operators which is blocking us from encrypting those fields using shield platform encrption in salesforce as The operator like is not supported on an encrypted field

   Can we modify the apex classes to stop filtering by like operator

   Apex Class: BoxFileService, line 167, column 36: The operator like is not supported on an encrypted field
   Apex Class: BoxAILWCControllerEnhancedTests, line 114, column 31: The operator like is not supported on an encrypted field
   Apex Class: BoxAILWCControllerEnhancedTests, line 130, column 31: The operator like is not supported on an encrypted field
   Apex Class: BoxFileService, line 156, column 36: The operator like is not supported on an encrypted field

   n my Salesforce Org ha we have Box managed package installed, some apex classes as part of package BoxAILWCControllerEnhancedTests, BoxFileService are using account and contact name fields in soql queries with like operators which is blocking us from encrypting those fields using shield platform encrption in salesforce as The operator like is not supported on an encrypted field

   Can we modify the apex classes to stop filtering by like operator

   Apex Class: BoxFileService, line 167, column 36: The operator like is not supported on an encrypted field
   Apex Class: BoxAILWCControllerEnhancedTests, line 114, column 31: The operator like is not supported… more

   1 vote

   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

5. Create More Filters for User Details Reporting

   I am looking to have a User Details report automatically filter out platform users from managed users. Additionally, I'd like to see some other configurations of user outputs:

   All Users (managed, unmanaged, external, and platform users)
   Managed Users (managed users ONLY [without platform users])
   Platform Users (only platform users)
   Unmanaged Users (unmanaged users)
   External Users (external users)
   Managed and Unmanaged (managed [not platform] and unmanaged users)
   Managed and Platform Users (managed users report as of today)

   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

6. When my sidebar is expanded in Box, my entire Box window experiences a glitch that makes the entire screen strobe back and forth

   When my sidebar is expanded in Box, my entire Box window experiences a glitch that makes the entire screen strobe back and forth until I collapse the sidebar. It is extremely irritating and often I want the sidebar open so I can see details about an item.

   1 vote

   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

7. File Request to allow global template

   Allow File Request Request to suggest template from what has been used previously or templates used at parent or root directory level.

   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  ·  Uploads  ·  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. File Request to allow file extension allow listing

   File Request should allow to set the acceptable file extensions to prevent user from uploading random file.

   1 vote

   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  ·  Uploads  ·  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. Hover over file name

   I see that a hover option to view whole file names was offered in 2022. This used to work fine for me but recently stopped. I can no longer hover to see whole file names and have to go back to opening the doc to view full names. Am I the only one having this problem or did it stop for everyone?

   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  ·  Web App  ·  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. Show Folder size

    Please add feature to show size of a folder not just number of files.

    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  ·  Web App  ·  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. 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

12. 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

13. AI Studio - permissioning for Agent creator

    When creating an Agent in AI Studio, it's not clear that permission is not automatically granted to the Agent creator. It would be helpful to add help text indicating that if an Agent creator needs access to that Agent, they should provide themselves permission alongside other users who are being granted access.

    1 vote

    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  ·  AI Studio  ·  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. Per-Application Control for AI API

    【Current Behavior】
    The AI API setting in the Admin Console is currently a tenant-wide
    toggle (ON/OFF). Once enabled, all custom applications (both
    Server Authentication and OAuth 2.0 apps) under the enterprise
    can invoke AI API endpoints. There is no mechanism to permit or
    restrict AI API usage on a per-application basis.

    【Problem / Business Impact】
    Because AI API consumption is billable, administrators cannot
    selectively allow AI API access only for specific sanctioned
    applications while blocking others. This creates the following
    risks:

    1. Uncontrolled billing exposure: Any application with AI API scope enabled can trigger consumption that the administrator did not sanction, leading to unexpected charges.
    2. Blocked adoption: To avoid unintended billing, customers are forced to keep AI API disabled at the tenant level, which prevents legitimate, pre-approved applications from leveraging AI API capabilities.
    3. Lack of governance: Administrators have no way to audit or enforce which applications are permitted to consume AI API resources, conflicting with standard enterprise governance requirements.

    As a result, customers who want to pilot AI API with a limited
    scope, or who want to separate billable vs. non-billable
    application usage, cannot proceed.

    【Requested Feature】
    Introduce per-application control for AI API access. Specifically:

    • In the Admin Console (or Developer Console application management), allow administrators to explicitly allow or deny AI API access for each individual custom application.
    • The setting should override the tenant-wide toggle, or at minimum be evaluated in addition to it, so that administrators can maintain a default-deny posture while whitelisting specific applications.
    • Provide visibility (e.g., via Admin Console or reporting) into which applications are currently permitted to consume AI API.

    【現状の挙動】
    管理コンソールのAI API設定は、テナント単位のON/OFFトグルのみ
    提供されています。有効化すると、当該エンタープライズ配下の
    全てのカスタムアプリケーション（Server Authentication および
    OAuth 2.0 アプリケーションの双方）がAI APIエンドポイントを
    呼び出し可能となります。アプリケーション単位でAI APIの
    利用可否を制御する手段は存在しません。

    【課題・ビジネスインパクト】
    AI APIは従量課金対象であるため、管理者が承認した特定の
    アプリケーションのみにAI API利用を許可し、それ以外を制限する
    という運用が現状では不可能です。これにより、以下のリスクが
    発生しています。

    1. 意図しない課金の発生：AI APIスコープが有効な全ての アプリケーションが課金対象の処理を実行可能であり、 管理者が認知しないAI API課金が発生する可能性がある。
    2. 利用機会の喪失：意図しない課金を回避するため、テナント 単位でAI APIをOFFのまま運用せざるを得ず、本来承認済みの アプリケーションにおいてもAI API機能を活用できない。
    3. ガバナンスの欠如：どのアプリケーションがAI APIを利用して いるかを管理者が制御・監査する手段がなく、エンタープライズ における標準的なガバナンス要件を満たせない。

    結果として、限定的なスコープでAI APIを試行したい、あるいは
    課金対象アプリと非対象アプリを分離して管理したい顧客が、
    AI APIの採用判断に至れない状況が発生しています。

    【要望機能】
    AI APIアクセスをアプリケーション単位で制御する機能の実装を
    要望します。具体的には以下の通りです。

    ・管理コンソール（または開発者コンソールのアプリケーション
    管理画面）において、個別のカスタムアプリケーションごとに
    AI APIの利用可否を明示的に許可／拒否できるようにする。
    ・当該設定はテナント単位のトグルを上書きする、もしくは
    併せて評価される仕様とし、管理者がデフォルト拒否を維持
    しつつ特定アプリケーションをホワイトリスト化できる運用を
    可能とする。
    ・現時点でAI API利用が許可されているアプリケーションを
    管理コンソールまたはレポート機能から可視化できるように
    する。

    【Current Behavior】
    The AI API setting in the Admin Console is currently a tenant-wide
    toggle (ON/OFF). Once enabled, all custom applications (both
    Server Authentication and OAuth 2.0 apps) under the enterprise
    can invoke AI API endpoints. There is no mechanism to permit or
    restrict AI API usage on a per-application basis.

    【Problem / Business Impact】
    Because AI API consumption is billable, administrators cannot
    selectively allow AI API access only for specific sanctioned
    applications while blocking others. This creates the following
    risks:

    1. Uncontrolled billing exposure: Any application with AI API scope enabled can trigger consumption that the administrator did not sanction,… 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  ·  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

15. Switch to Cloud File API for Drive to solve the Icons not showing issue

    Like many users I found that the status icons disappeared in Explorer after starting an addition cloud service on Windows 11. This issue is well documented here: https://support.box.com/hc/en-us/articles/360044195513-Icons-Do-Not-Appear-In-Box-Drive-or-Box-Sync-on-Windows

    I would like to suggest utilizing the newer "cloud files API" provided by Microsoft that is used by OneDrive to move the icons to a status category rather than icons on the file thumbnails/icons.

    The documentation can be found here; https://learn.microsoft.com/en-us/windows/win32/cfapi/build-a-cloud-file-sync-engine

    Thank you for your consideration.

    1 vote

    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

16. I want to be able to show or hide the content displayed in the root folder

    Since you are invited to many folders in the company, a large number of folders will appear in the root folder (folder/0).
    I want a function that allows me to show and hide so that only the folders I need are displayed.

    タイトル：
    ルートフォルダに表示されているコンテンツの表示・非表示を切り替えられるようにしたい
    本文：
    社内で多くのフォルダに招待されるため、ルートフォルダ（folder/0）に大量のフォルダが表示されてしまう。
    必要なフォルダのみを表示させるよう、表示・非表示を切り替えられる機能が欲しい。

    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

17. I want you to be able to add folders that are not owned or co-owned to Box Hubs

    Many of the folders I use have editor permissions, and the current specifications do not allow me to use Hubs
    I want you to be able to add editor permissions folders to Hubs as well.

    タイトル：
    所有者・共同所有者ではないフォルダーもBox Hubsに追加できるようにしてほしい
    本文：

    1 vote

    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 Hubs  ·  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
    not planned  ·  AdminAnonymous (Admin, Box) responded

    Unfortunately, we won't implement this as this contradicts Hubs security policy.

18. Audit log for changes to Hub settings.

    I would like changes to the “Hubs Global Presets” or “Hub Settings” to be recorded in the security log.
    Even if we apply restrictions on collaboration and shared links, there is currently no way to trace what happened when those restrictions are somehow removed. From a security and compliance standpoint, not being able to review an audit trail of these operations poses a significant risk.

    （日本語）
    「Hubs全体のプリセット」もしくは「Hubsの設定」を変更した際、セキュリティログに記録してほしいです。
    コラボレーションや共有リンクに制限をかけていても、何らかの理由でその制限が外れてしまった場合、現状では経緯を追跡する手段がありません。セキュリティやコンプライアンスの観点から、これらの操作履歴を確認できないことは、非常に大きなリスクです。

    8 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

19. Enforce signer-only access and security controls in Box Sign

    It would be helpful to have the ability to restrict access to Box Sign documents to signers only.

    Currently, additional protections such as password or login can be configured, but access itself is not strictly limited to the intended signers, which may create a risk of unintended access.

    It would be great if admins could enforce signer-only access at the organizational level, ensuring that only designated signers can view the documents sent via Box Sign.

    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 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

20. Adding direct links dialog to the shared links dialog popup

    There really needs to be a way that the direct links dialog could be moved to the Shared Links dialog box so that you don't have to have multiple click to just to get a direct link to an image file. At the current time, it's a lengthy process to create direct image links. See the attached files and please fix this!

    •  

    •  

    1 vote

    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  ·  Content Manager  ·  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