9983 results found

1. Can we get the ability to set which agent is the default agent per hub?

   It would be great if we could set which agent is the default for each hub. If left blank, then the default Box agent is selected. If we have an agent for each hub, our users may forget to switch the agent as they switch between hubs.

   21 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  ·  1 comment  ·  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

2. Invite Box Groups from Another Tenant

   Currently, when inviting users who belong to a different tenant to our tenant, each user must be invited individually. This process is time-consuming and inefficient.
   We would like the ability to invite users from another tenant by group, rather than having to invite them one by one.

   （InJapanese）
   別テナントからBoxグループを招待したい

   現状別テナントに所属しているユーザを弊社テナントへ招待する場合、1ユーザずつ招待する必要があり、対応に時間がかかり非効率です。
   ユーザーを1人ずつ招待するのではなく、別テナントのユーザをグループ単位で招待できる機能を希望します。

   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  ·  Other  ·  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. AI chat history should be saved

   Any AI chat history, whether on a document(s) or in a Hub, is not saved in the same way other AI platforms do (ex, ChatGPT, Google Gemini, CoPilot, Perplexity, etc.). Retaining the chat history will improve efficiency in future conversations and improve personalization. This seems to be the biggest flaw/miss in the rollout of Box AI.

   25 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

   on roadmap  ·  1 comment  ·  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

4. Admin controls for the Solutions menu

   We would like Box Admins to have the ability to manage the Solutions menu in the Box web app.

   The Solutions menu can create confusion because it allows end users to contact Box Consulting directly, which may bypass internal IT, helpdesk, procurement, or governance processes.

   Please consider adding admin controls to either:

   1) Enable or disable the Solutions menu for the enterprise
   2) Replace the default Box Consulting contact path with an internal helpdesk or support contact, similar to the support contact email setting in Admin Console (Custom Settings)

   This would help to route end user inquiries through the right internal channels while still allowing access to Solutions where appropriate.

   We would like Box Admins to have the ability to manage the Solutions menu in the Box web app.

   The Solutions menu can create confusion because it allows end users to contact Box Consulting directly, which may bypass internal IT, helpdesk, procurement, or governance processes.

   Please consider adding admin controls to either:

   1) Enable or disable the Solutions menu for the enterprise
   2) Replace the default Box Consulting contact path with an internal helpdesk or support contact, similar to the support contact email setting in Admin Console (Custom Settings)

   This would help to route end user inquiries through the right… 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  ·  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

5. Date and TimeStamp - Box Sign

   Add date and timestamp on the signature field is currently and enterprise setting. The user would like for this to be user facing, instead of enterprise wide. So that individual users could choose to toggle on or off. Or specific users and groups

   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

6. 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アクション程度まで拡張いただけると、このようなユースケースに対応でき、大規模な業務プロセスをワークアラウンドや複雑なフロー分割なしで実装できるようになります。

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

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

7. No emails when a group is added to a Box Hub

   I was surprised that I accidentally triggered an email to all members when adding a group as a collaborator to a Box Hub- this does not typically happen with folders. I would like an option to suppress this.

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

8. Automatically Trim Whitespace Around Uploaded Signature or Allow Signer to Crop
   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 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

9. ability to select a source folder and have the outcome automatically include all subfolders

   In Box Automate, I created a custom extract agent and selected a source folder. However, after reviewing the run history, I noticed that only the files in the top-level source folder are processed, while files in subfolders are ignored. I would like the ability to select a source folder and have the agent automatically include all subfolders within it or give you the option to include them.

   We currently have a couple scenarios where we would like to run extraction on existing files and folders in a parent folder retroactively, not just new uploads.

   Thank you, and please let me know if you need any additional details.

   In Box Automate, I created a custom extract agent and selected a source folder. However, after reviewing the run history, I noticed that only the files in the top-level source folder are processed, while files in subfolders are ignored. I would like the ability to select a source folder and have the agent automatically include all subfolders within it or give you the option to include them.

   We currently have a couple scenarios where we would like to run extraction on existing files and folders in a parent folder retroactively, not just new uploads.

   Thank you, and please let me… 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

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

10. Signer to add fields to the signature request additionally to those added by sender

    When using BoxSign, there are many cases where the requester will add additional fields.
    In such a situation, there are times when signers themselves would like to add new fields, but they are unable to do so, and many voices are voicing concerns about the lack of convenience across the company.
    We would like to request the implementation of this feature to improve convenience.

    BoxSignを使用する際に署名リクエスト者がフィールドを追加するケースが多々あります。
    その状況下で署名者自身でも新たなフィールドを追加したい時がありますが、追加することできず社内全体で利便性に欠けている声が多く上がっています。
    利便性向上のため本機能の実装をお願いしたいです。

    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

    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

11. Provide a Command/API to Log Out from Box Drive

    Background:
    There is currently no command or API available to log out from Box Drive programmatically.

    Request:
    We would like to request the addition of a command or API that allows users to log out from Box Drive remotely. This would be particularly valuable for enterprise IT administrators who need to immediately terminate Box Drive sessions and clear local cache in the event of a device theft.

    Use Case:
    - Remote logout of Box Drive when a PC is stolen, to prevent unauthorized access to corporate data stored in Box
    - Clearing the local Box Drive cache remotely to ensure that no locally synced files remain accessible on the stolen device

    Thank you for your consideration.

    Background:
    There is currently no command or API available to log out from Box Drive programmatically.

    Request:
    We would like to request the addition of a command or API that allows users to log out from Box Drive remotely. This would be particularly valuable for enterprise IT administrators who need to immediately terminate Box Drive sessions and clear local cache in the event of a device theft.

    Use Case:
    - Remote logout of Box Drive when a PC is stolen, to prevent unauthorized access to corporate data stored in Box
    - Clearing the local Box Drive cache remotely to ensure… 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  ·  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

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

    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

13. Request for Hubs Version History Feature

    Customer Pain Point & Concern:
    Our customer is highly concerned about the risk of editors accidentally deleting or overwriting pages or sections within Hubs. Currently, there is no built-in version control or version history feature for Hubs (similar to what is available in Box Notes). As a workaround to prepare a backup plan, they are currently forced to take manual, regular backups by copying content, which has proven to be extremely tedious and inefficient.

    Requested Feature:

    Version History for Hubs: A feature similar to Box Notes that allows users to view, restore, and revert to older versions of Hubs pages and sections.
    This is a critical requirement for this large-scale customer to ensure secure content management and operational efficiency. We would highly appreciate it if this could be considered for the product roadmap.

    Thank you for your support!

    Customer Pain Point & Concern:
    Our customer is highly concerned about the risk of editors accidentally deleting or overwriting pages or sections within Hubs. Currently, there is no built-in version control or version history feature for Hubs (similar to what is available in Box Notes). As a workaround to prepare a backup plan, they are currently forced to take manual, regular backups by copying content, which has proven to be extremely tedious and inefficient.

    Requested Feature:

    Version History for Hubs: A feature similar to Box Notes that allows users to view, restore, and revert to older versions of Hubs pages… 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  ·  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

14. Enable selecting files stored in Box directly in File Requests

    Currently, file request links only allow you to upload files from local folders.
    This is convenient if you use Box Drive, but users who rely solely on the browser have to download files from Box and then re-upload them via the file request link.

    I would like the file selection for file requests to allow choosing not only folders on the PC, but also files already stored in Box directly from the browser interface.

    〈ファイルリクエストでBox内ファイルを直接選択可能にしたい〉
    現在、ファイルリクエストリンクでは、ローカルフォルダ内のファイルしかアップロードできません。
    Box Drive を利用している場合は便利ですが、ブラウザのみを利用するユーザーは、いったん Box からファイルをダウンロードしてから、ファイルリクエストリンクへ再度アップロードする必要があります。

    ファイルリクエストでアップロードするファイルの選択時に、PC上のフォルダだけでなく、ブラウザ画面から Box 内に保存されているファイルも直接選べるようにしてほしいです。

    •  

    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  ·  Other  ·  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. Add a normal Search Bar to Hubs

    The AI is not great. I have written instructions for staff to follow to troubleshoot something. The AI mixes steps and adds incorrect information so that it makes it useless.
    We need a normal Search Bar that can be typed into to find matching key words. It can just have up and down arrows just like "find in page" that allow you to skip through the hub to the related content.

    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

    2 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

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

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

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

18. Reverse Image Search

    Being able to upload an image and Box browser finding it (or similar) within a specified folder. Similar idea to Google lens.

    67 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  ·  4 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

19. Exclude Specific Content from Box AI

    As a law firm we need to segregate certain client data from the ability to use Box AI due to legal agreements in place with their clients to not be able to use AI on their data. Currently we would need to turn off Box AI on the whole account in order to achieve this requirement, which is not ideal.

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

20. test flow

    testing flow

    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

    2 comments  ·  Other  ·  Edit…  ·  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