9985 results found

1. New Box Drive for Windows (Cloud Files): Improve Explorer UX during startup/connecting to avoid unstable/incorrect folder state

   Problem (What problem could Box solve for you?)
   When Windows starts, the new Box Drive (Cloud Files architecture) auto-connects. During this “connecting/initializing” period, the Box Drive folder becomes visible in File Explorer even though Box Drive is not fully running/ready. The folder view is unstable: some items show missing icons/status, and opening folders can result in errors. This happens consistently across multiple users in our pilot.
   This behavior may be aligned with the feature “Box Drive folders remain accessible even when the Box Drive application is not running,” but exposing a partially-initialized state causes confusion and support tickets (users think Drive is broken or content is missing).

   Proposed improvement
   Please improve the File Explorer experience while Box Drive is starting/connecting/initializing so users do not see an unstable or misleading folder state. For example:
   Show a clear “Box Drive is connecting/initializing” placeholder and block navigation until ready; and/or
   Provide an admin/user option to delay/hide the Box Drive mount until Drive is connected; and/or
   Ensure cached vs. not-yet-available content is clearly indicated without throwing generic Windows errors.

   Steps to reproduce
   1.Install new Box Drive for Windows (Cloud Files architecture), version 2.48 (pilot).
   2.Ensure Box Drive is configured to auto-start on Windows login.
   3.Reboot the PC and open File Explorer immediately after login.
   4.Observe Box folder becomes visible before Drive is fully ready; icons may be missing/blank; opening folders may show errors.

   Impact
   ・End-user confusion (“Drive is broken”, “files disappeared”)
   ・Increased helpdesk tickets and delays in rollout/adoption of the new Box Drive

   The following is written in Japanese

   Windows 向け新しい Box Drive（Cloud Files）：起動／接続時にエクスプローラーの UX を改善し、不安定または誤ったフォルダー状態を回避する

   問題（Box はどのような課題を解決できるか？）
   Windows の起動時に、新しい Box Drive（Cloud Files アーキテクチャ）が自動接続します。この「接続／初期化」中、Box Drive がまだ完全に起動・準備完了していないにもかかわらず、File Explorer に Box Drive フォルダーが表示されます。フォルダー表示が不安定で、一部の項目でアイコン／ステータスが表示されないことがあり、フォルダーを開くとエラーになる場合があります。この現象はパイロットに参加している複数ユーザーで一貫して発生しています。この挙動は「Box Drive アプリケーションが起動していない場合でも Box Drive フォルダーにアクセス可能」という機能仕様に沿っている可能性がありますが、部分的に初期化された状態が見えてしまうことで混乱を招き、サポートチケットの増加につながっています（ユーザーが「Drive が壊れている」「コンテンツが消えた」と誤解する）。

   改善案
   Box Drive の起動／接続／初期化中に、File Explorer 上で不安定または誤解を招く状態が見えないよう、エクスペリエンスを改善してください。例：
   ・「Box Drive は接続／初期化中です」という明確なプレースホルダーを表示し、準備完了までナビゲーションをブロックする
   ・Drive が接続されるまで Box Drive のマウントを遅延／非表示にする管理者／ユーザー向けオプションを提供する
   ・キャッシュ済みコンテンツと、まだ利用できないコンテンツを明確に区別して表示し、一般的な Windows エラーを出さないようにする

   再現手順
   1.新しい Box Drive for Windows（Cloud Files アーキテクチャ）v2.48（パイロット）をインストールする
   2.Windows ログイン時に Box Drive が自動起動するよう設定する
   3.PC を再起動し、ログイン直後に File Explorer を開く
   4.Drive が完全に準備完了する前に Box フォルダーが表示されることを確認する（アイコンが欠落／空白になる場合がある）。接続中の状態でフォルダーを開くとエラーが出る場合がある

   影響
   ・エンドユーザーの混乱（「Drive が壊れている」「ファイルが消えた」）
   ・ヘルプデスク問い合わせの増加、および新しい Box Drive の展開／定着の遅延

   Problem (What problem could Box solve for you?)
   When Windows starts, the new Box Drive (Cloud Files architecture) auto-connects. During this “connecting/initializing” period, the Box Drive folder becomes visible in File Explorer even though Box Drive is not fully running/ready. The folder view is unstable: some items show missing icons/status, and opening folders can result in errors. This happens consistently across multiple users in our pilot.
   This behavior may be aligned with the feature “Box Drive folders remain accessible even when the Box Drive application is not running,” but exposing a partially-initialized state causes confusion and support tickets (users… 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 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

2. Box MCP Connector: Add Binary File Upload Support (.xlsx, .pptx, .docx)

   The Problem
   The Box MCP (Model Context Protocol) connector, used to integrate Box with AI platforms like Claude (Anthropic), currently supports only plain-text file uploads. The uploadfile and uploadfileversion tools accept text-only content and support a limited set of extensions: txt, md, csv, html, json, and a few others.
   Binary file formats — specifically .xlsx, .pptx, and .docx — cannot be uploaded through the MCP connector. The connector's own documentation references a getupload_url path for binary uploads, but that method is not exposed as a callable tool in the current implementation.

   Why This Matters
   AI-assisted workflows are increasingly the norm for SMB and enterprise teams. When an AI tool generates a finished Excel model, PowerPoint deck, or Word document, users expect it to land directly in Box, just as it would if they saved it manually. Instead, they're forced to download the file from the AI interface and drag it into Box Drive by hand. That's friction that breaks the workflow and defeats the purpose of the integration.
   For comparison, major document-sharing platforms work without problems.

   What We're Asking For
   Enable binary file upload support in the Box MCP connector for common formats, including .xlsx, .pptx, and .docx.

   Who This Affects
   Any team using Box alongside an AI platform (Claude, Copilot, custom GPTs, or any MCP-compatible tool) that generates Office-format files. This is a growing segment — and right now, Box is the bottleneck in every one of those workflows.
   Please upvote if your team runs into this. The fix is well-defined, and the precedent already exists in competing connectors.

   The Problem
   The Box MCP (Model Context Protocol) connector, used to integrate Box with AI platforms like Claude (Anthropic), currently supports only plain-text file uploads. The uploadfile and uploadfileversion tools accept text-only content and support a limited set of extensions: txt, md, csv, html, json, and a few others.
   Binary file formats — specifically .xlsx, .pptx, and .docx — cannot be uploaded through the MCP connector. The connector's own documentation references a getupload_url path for binary uploads, but that method is not exposed as a callable tool in the current implementation.

   Why This Matters
   AI-assisted workflows… 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  ·  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

3. AI Units Usage Reporting

   When AI activity is included in a User Activity report, the number of AI units consumed should also be included. Another idea is to add an AI Units report that lists all activity that consumes AL Units.

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

4. Update Box AI Studio configuration

   Update AI Studio configuration in the admin console to be consistent with other AI features and features in Box to have the option for Enable for all, Disable for all, Enable for specific users, and disable for specific users

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

5. Add file and folder move operations to the Box integration for ChatGPT/OpenAI

   Subject: Add file and folder move operations to the Box integration for ChatGPT/OpenAI

   Hello Box Support,

   I am using the official Box integration within ChatGPT. The integration can currently list my files, create folders, upload files, rename items, and inspect permissions. However, it does not provide an action for moving an existing file or folder to another Box folder.

   For example, I asked ChatGPT to:

   1. Create a folder named !
   2. Move the files and folders in my Box root directory into that folder

   ChatGPT successfully created the folder, but it could not move the existing items because the Box integration did not expose a file or folder move operation.

   I confirmed that this is not an account-permission issue. I own the files, and my Box permissions allow deleting, downloading, renaming, uploading, and sharing them.

   Could you please clarify:

   1. Is the absence of file and folder move operations an intentional security restriction?
   2. Is this limitation controlled by Box, OpenAI, or the configuration of the Box connector/MCP integration?
   3. Could Box add supported actions for:

   • Moving a file to another folder
   • Moving a folder to another folder
   • Moving multiple selected items in one operation
     1. Could the integration use Box’s normal item-update API while respecting the user’s existing Box permissions and requesting confirmation before moving multiple items?

   This capability is important because without move operations, ChatGPT can inspect and create Box content but cannot perform basic file organization workflows.

   Please forward this as a feature request to the team responsible for the Box integration with OpenAI/ChatGPT.

   Thank you.

   Subject: Add file and folder move operations to the Box integration for ChatGPT/OpenAI

   Hello Box Support,

   I am using the official Box integration within ChatGPT. The integration can currently list my files, create folders, upload files, rename items, and inspect permissions. However, it does not provide an action for moving an existing file or folder to another Box folder.

   For example, I asked ChatGPT to:

   1. Create a folder named !
   2. Move the files and folders in my Box root directory into that folder

   ChatGPT successfully created the folder, but it could not move the existing items because the Box integration… 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  ·  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

6. Large Folder Operation proactive notification and approval request

   Provide a notification to a user should they be attempting to perform a Large Folder Operation and request admin approval for the action for an audit trail

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

7. Default agent for hub

   I want to be able to create a custom agent and set it as the default agent for a hub. The idea is that if I want a hub to return a consistent result every time someone searches it, I can build an agent that provides that experience and have that agent automatically selected as the hub’s default. I do not want users to have to choose which agent to use.

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

8. Real-time visibility of whether a user has external collaborations ユーザーが外部コラボレーションを行っているかをリアルタイムで確認する機能

   ・Problem Statement / 課題
   In the legacy Content Manager, an admin could see — in real time — that a managed user had a folder collaborated with an external party, along with the owner name. This was used as a pre-check before deleting/offboarding the user. The new Content Manager no longer surfaces external folders, so this real-time check is no longer possible through the UI.
   レガシーContent Managerでは、管理者は対象ユーザーが外部とコラボレーションしているフォルダの存在と所有者名を、リアルタイムで確認できました。これはユーザーの削除/オフボーディング前の事前チェックとして使われていました。新Content Managerでは外部フォルダが表示されなくなったため、このリアルタイム確認がUI上で行えなくなっています。
   Note: This request is not specifically about Content Manager. The legacy CM simply happened to be where this was possible. We are requesting the capability (real-time admin-side visibility of a user's external collaboration status), regardless of where in the product it is surfaced (Admin Console, a dedicated view, etc.).
   補足：本要望はContent Managerに限定したものではありません。 レガシーCMがたまたまそれを実現できる場所だっただけです。要望しているのは「管理者側でユーザーの外部コラボレーション状況をリアルタイムに把握できる機能そのもの」であり、提供場所（Admin Console、専用ビュー等）は問いません。

   ・Requirements (phased) / 要件（段階別）
   The top priority is real-time confirmation of a user's external-collaboration status. Reporting (with up to 24h delay) does not satisfy this.
   最優先事項は、ユーザーの外部コラボレーション状況をリアルタイムで確認できることです。レポート（最大24時間の遅延あり）ではこれを満たしません。

   Phase 1 (minimum acceptable): For a given managed user, show in real time whether they have any external-folder collaboration (yes/no, existence only).
   Phase 2 (desired enhancement): Additionally show which external tenant(s) the user is collaborating with.
   第一段階（最低限）： 対象ユーザーについて、外部フォルダコラボレーションの有無をリアルタイムに表示する（yes/no、存在のみ）。
   第二段階（追加で望ましい）： 加えて、そのユーザーがどの外部テナントとコラボレーションしているかを表示する。

   ・Current Workaround and Its Limitations / 現行のワークアラウンドとその限界
   Affected customers are currently using the API (List items in folder against folderid: 0 / root) as a temporary workaround, expected to last only a few months. This is not a sustainable solution.
   該当顧客は現在、API（List items in folder を folderid: 0／ルートに対して実行）を一時的なワークアラウンドとして使用していますが、これは数か月程度の暫定策と想定されています。持続可能な解決策ではありません。
   Other admin-side options are insufficient for this use case:

   Reports: Content reports reflect data only up to ~24 hours before report run time (per Box Support, "Running Reports"). Content added in the last 24h can be missing → fails the real-time requirement.
   Instant Login (Admin Console): Does not work for external folders, so it cannot be used to verify external collaboration.

   その他の管理者側の選択肢は、本ユースケースには不十分です：

   レポート： コンテンツレポートはレポート実行時点の約24時間前までのデータしか反映しません（Box Support「Running Reports」より）。直近24時間に追加されたコンテンツが欠落しうるため、リアルタイム要件を満たしません。
   Instant Login（Admin Console）： 外部フォルダには機能しないため、外部コラボレーションの確認には使えません。

   ・Business Impact / ビジネスインパクト
   In Japan, external-collaboration visibility directly affects user-offboarding and license-seat management for customers with record-retention obligations. Without a real-time check, IT cannot confidently delete users (compliance risk per customer), which ties up limited license seats and creates operational friction. This pattern is likely to recur across regulated/large enterprises in the Japanese market, so the capability has value beyond a single account.
   日本では、外部コラボレーションの可視性が、記録保存義務を持つ顧客のユーザーオフボーディングおよびライセンスシート管理に直接影響します。リアルタイムの確認手段がないと、IT部門は確信を持ってユーザーを削除できず（顧客視点ではコンプライアンスリスク）、限られたライセンスシートが拘束され、運用上のフリクションが生じます。このパターンは日本市場の規制業界/大企業で繰り返し発生する可能性が高く、単一アカウントを超えた価値を持つ機能です。

   ・Problem Statement / 課題
   In the legacy Content Manager, an admin could see — in real time — that a managed user had a folder collaborated with an external party, along with the owner name. This was used as a pre-check before deleting/offboarding the user. The new Content Manager no longer surfaces external folders, so this real-time check is no longer possible through the UI.
   レガシーContent Managerでは、管理者は対象ユーザーが外部とコラボレーションしているフォルダの存在と所有者名を、リアルタイムで確認できました。これはユーザーの削除/オフボーディング前の事前チェックとして使われていました。新Content Managerでは外部フォルダが表示されなくなったため、このリアルタイム確認がUI上で行えなくなっています。
   Note: This request is not specifically about Content Manager. The legacy CM simply happened to be where this was possible. We are requesting the capability (real-time admin-side visibility of a user's external… 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  ·  Admin Console  ·  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

9. Increased Character Limit - Box Forms

   Please increase character limit to 1000 for Box Forms long text. We have questions in surveys that we are looking to send out via Box Forms that exceed the current, 100-character limit.

   •  

   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

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

10. Delete User App Authorization

    It would be nice to delete User App Authorization from the Admin Console. While Server App Authorization can be deleted by contacting support, User App Auth cannot.

    Disabling auth is a good temporary workaround, but when there are many user app auths it can get cluttered and difficult to manage.

    •  

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

11. Report on file insights for all files

    Currently you can only view file insights on an individual file, from the file details. I need the ability to view file insights for all files, in a single report.
    Add a reporting feature in the admin console for file insights, where fields can be selected to be included in the report or not: People, Previews, Views, Downloads, Comments, Edits, Last Viewed Date, etc. And a File insights report is generated for ALL files in Box.
    Having insights on individual files only makes it unfeasible to measure file utilization across the repo, at scale. How can we measure which files have high views and which are not being viewed at all, across the file corpus, without a report. Manually navigating to file insights for each individual file, exporting, then merging all reports, for hundreds or thousands of files, is not feasible. Please provide a report to deliver this

    Currently you can only view file insights on an individual file, from the file details. I need the ability to view file insights for all files, in a single report.
    Add a reporting feature in the admin console for file insights, where fields can be selected to be included in the report or not: People, Previews, Views, Downloads, Comments, Edits, Last Viewed Date, etc. And a File insights report is generated for ALL files in Box.
    Having insights on individual files only makes it unfeasible to measure file utilization across the repo, at scale. How can we measure which… 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  ·  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

12. Restrict Hub Shared Link Creation to Admins Only

    Many users can access a Hub via its shared link.

    However, because there is currently no way to identify or control users who access via shared links, we would like to only invite required users directly to the Hub and eliminate the risk of anyone else viewing it.

    Under the current behavior, even with the strictest settings, Hub co-owners can still create shared links.

    It would be very helpful to have a stronger restriction so that even Hub co-owners cannot create shared links for Hubs, and only admins (or a similarly restricted role) can do so.

    --
    Hubは共有リンク経由で多くのユーザーがアクセスできます。
    しかし、共有リンクからアクセスしたユーザーを確認し制御する方法が現状ないため、Hubには必要なユーザーを招待してそれ以外の人が見るリスクをなくしたいと考えています。
    現状の仕様では、どんなに強い制限にしてもHubの共同所有者は共有リンクを発行できてしまいます。
    Hubの共有リンクの発行は、Hubの共同所有者にもさせないように、さらに強い制限（管理者以外Hubの共有リンク発行不可）があると嬉しいです。

    Many users can access a Hub via its shared link.

    However, because there is currently no way to identify or control users who access via shared links, we would like to only invite required users directly to the Hub and eliminate the risk of anyone else viewing it.

    Under the current behavior, even with the strictest settings, Hub co-owners can still create shared links.

    It would be very helpful to have a stronger restriction so that even Hub co-owners cannot create shared links for Hubs, and only admins (or a similarly restricted role) can do so.

    --
    Hubは共有リンク経由で多くのユーザーがアクセスできます。
    しかし、共有リンクからアクセスしたユーザーを確認し制御する方法が現状ないため、Hubには必要なユーザーを招待してそれ以外の人が見るリスクをなくしたいと考えています。
    現状の仕様では、どんなに強い制限にしてもHubの共同所有者は共有リンクを発行できてしまいます。… 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  ·  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

13. Bring back "Open Containing Folder" to the top of the Box Note menu (or allow customization)

    Hi Box Team,

    I would like to share some feedback regarding the user interface of Box Notes.

    Previously, the option to open the folder containing the current Box Note was located right at the top of the hamburger menu. This was incredibly convenient. However, with recent updates, this option has been pushed further and further down the list.

    To be honest, actions like viewing comments or inserting images are rarely used in my daily workflow compared to navigating back to the source folder. Having to scroll down every single time just to open the folder has made the user experience quite frustrating.

    I would highly appreciate it if you could consider one of the following improvements:

    Restore the original layout: Move the "Open Containing Folder" option back to the top of the menu.

    Add customization: Allow users to reorder or customize the menu items based on their workflow.

    Add a shortcut: Implement a dedicated shortcut button (or hotkey) on the main interface to open the parent folder directly.

    Thank you for your time and for continuously improving Box!

    Hi Box Team,

    I would like to share some feedback regarding the user interface of Box Notes.

    Previously, the option to open the folder containing the current Box Note was located right at the top of the hamburger menu. This was incredibly convenient. However, with recent updates, this option has been pushed further and further down the list.

    To be honest, actions like viewing comments or inserting images are rarely used in my daily workflow compared to navigating back to the source folder. Having to scroll down every single time just to open the folder has made the user experience… 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  ·  Box Notes  ·  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. Using public Beta for Folder Insights with Editor permissions

    Most users who need Folder Insights are editors.
    Also, invitations are often restricted for security reasons.
    I would like to see Folder Insights and reports downloadable even for invite-restricted editors.

    -in Japanese-
    フォルダインサイトを必要としているユーザーの多くは編集者権限であり、
    またセキュリティ上の理由から招待を制限されていることが多い。
    招待制限されている編集者権限でもフォルダインサイトの閲覧とレポートのダウンロードができるようにしてほしい。

    34 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

    gathering feedback  ·  1 comment  ·  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

15. share app dashboards with external users

    It would be great to be able to share Apps dashboard with external users just like you can a file/folder/Hub today. Use case is we work with lots of external suppliers and an Apps dashboard would make collaboration much easier.

    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 Apps  ·  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. Delete or hide Source Systems without having to delete all associated jobs

    The process to delete a Shuttle Windows source is to first manually locate and delete all completed Shuttle jobs that ran under that source, then delete the source server via the trash can button when selecting a source system via the new job wizard. Box Support have confirmed this experience.

    Box Shuttle admins should be able to delete, or at least hide a source system, as part of clean-up activities, without having to manually export (if needed) and delete all previously configured jobs which is a frustrating user experience that introduces a lot of extra, hard-to-justify work on the admin side.

    The process to delete a Shuttle Windows source is to first manually locate and delete all completed Shuttle jobs that ran under that source, then delete the source server via the trash can button when selecting a source system via the new job wizard. Box Support have confirmed this experience.

    Box Shuttle admins should be able to delete, or at least hide a source system, as part of clean-up activities, without having to manually export (if needed) and delete all previously configured jobs which is a frustrating user experience that introduces a lot of extra, hard-to-justify work on the admin… 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  ·  Shuttle  ·  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. Improve Box Shuttle Filter to search by Source System

    I'd like to be able to filter the Shuttle job list on the name of a source system.

    This requirement is derived as a result of a product limitation where source systems cannot be deleted unless all completed jobs are deleted. Without this filter option, finding and deleting all jobs associated with a single source system is extremely laborious.

    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  ·  Shuttle  ·  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. Enhance Sorting by “Hub Name” in Hub View

    In the current Hub list view, users can only sort by “Last updated” or “Views.”

    Some organizations define naming rules for Hubs, and in those cases, being able to sort by “Hub name” would make the Hub view much easier for users to navigate and understand.

    ユーザーのHub一覧画面を見たとき、現在は「更新日」「閲覧数順」でしか並べ替えることができません。
    Hub名で並び替えたいです。これが実現すればユーザーはビュー画面を見やすくすることができます

    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

19. Enhanced Hub Reporting

    Content published to Hubs can be previewed across folders by any user who has access to the Hub, regardless of their folder-level permissions. While this is a great strength of Hubs, it also introduces security risks.

    The current Hub reporting is not sufficient for Box Admins to properly manage this. Box Admins would like to regularly review the content published to Hubs in order to mitigate security risks.

    If more detailed reporting were available, Admins could, for example, generate lists by Hub owner and ask each Hub owner to review and clean up their own Hubs.

    Example fields:

    Hub title
    Hub owner
    Published content name
    Folder
    Parent folder
    …etc.

    Hubに掲載されたコンテンツは、Hubへのアクセス権があるユーザーはフォルダの権限に関わらず横断的にプレビューできてしまいます。
    これはHubのいい点でもありますが、セキュリティリスクでもあります。
    現在のHubレポートではBox管理者が管理するためには不十分です。
    Box管理者は定期的にHubに掲載されているコンテンツの確認をして、それが適切かを判断し、セキュリティリスクを軽減したいです。
    Hubレポートでコンテンツの情報が取得できれば、管理者はHubの作成者別にリストを配布して、Hub作成者自身で整理してもらうことが可能になります

    Content published to Hubs can be previewed across folders by any user who has access to the Hub, regardless of their folder-level permissions. While this is a great strength of Hubs, it also introduces security risks.

    The current Hub reporting is not sufficient for Box Admins to properly manage this. Box Admins would like to regularly review the content published to Hubs in order to mitigate security risks.

    If more detailed reporting were available, Admins could, for example, generate lists by Hub owner and ask each Hub owner to review and clean up their own Hubs.

    Example fields:

    Hub title… 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  ·  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

20. Workflow Management Report

    The new Automate features are much more powerful than the previous Relay, and I’m excited to start using them going forward. After enabling Automate, I expect many users will create workflows, so the number of workflows in a tenant will increase significantly.

    Currently, I can visually check the workflows created in a tenant from the admin console, but as the number of workflows grows, it becomes difficult to review them all and properly manage them.

    It would be very helpful to have a way to export or list all workflows that exist in a tenant.

    Example fields:
    Workflow name
    Creator
    Creation date
    Last updated date
    Last run date
    Total number of runs in the past
    …etc.

    ---

    Automate機能を有効化後、ユーザーが自身でたくさんワークフローを作成すると想定されます。そのため、テナントの中でワークフロー数が増加する見込みです。
    しかし、現在は管理コンソール上のUIで目視確認するしかなく、ワークフロー数が増加すると管理が困難になっています。
    テナント上にあるワークフローを以下のような項目で出力できるとより便利です。

    項目例：ワークフロー名/作成者/作成日/更新日/直近利用日/過去実施回数…など

    The new Automate features are much more powerful than the previous Relay, and I’m excited to start using them going forward. After enabling Automate, I expect many users will create workflows, so the number of workflows in a tenant will increase significantly.

    Currently, I can visually check the workflows created in a tenant from the admin console, but as the number of workflows grows, it becomes difficult to review them all and properly manage them.

    It would be very helpful to have a way to export or list all workflows that exist in a tenant.

    Example fields:
    Workflow name
    Creator… 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  ·  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