Help shape the future of Box
Welcome to Box Pulse, our product feedback tool powered by UserVoice. Got an idea for how to improve Box? Share it with us and gather support or vote on other people's ideas. Your feedback is essential to informing roadmap decisions and shaping the future of our products. Thanks for joining our community!
See user guide here.
- or
21 results found
-
I want Japanese mark of a voiced sound in speech characters to be unified with NFC.
I want Japanese mark of a voiced sound in speech characters to be unified with NFC.
-Overview-
example: the 'ga' syllabary series in the Japanese alphabet
'ガ'is U+30AC on windows or unix/linux
-> NFC(Normalization Form Canonical Compression)
'ガ'is U+30AB U+3099U on mac OSX
-> NFD(Normalization Form Canonical Decompression)As you know, mac OSX use only NFD.
Windows use NFC usually, but NFD can be used at the same time.When trying to share BOX folder between Win and mac, Inconvenience occurs.
-problem-
First
In Windows explorer, NFC and NFD are displayed as the same character on the screen, so they are indistinguishable.The second
In Adobe InDesign, image files are managed as "link files", but file names are managed by NFC, so upload InDesign data created on mac OS to the shared BOX folder and download it on Windows. Cutting file link will occur.The third
Where NFC uses one character in UTF-8, NFD uses two characters in UTF-8.
The file "がぎぐげござじずぜぞだぢづでどばびぶべぼぱぴぷぺぽガギグゲゴザジズゼゾダヂヅデドバビブベボパピプペポヴ.txt" can be used on macOSX, but this file cannot be saved on the BOX server by Finder using BOX Drive.
Even if two characters are used, "xx.txt" uses only 106 characters.
And from Windows PC,
The file "がぎぐげござじずぜぞだぢづでどばびぶべぼぱぴぷぺぽガギグゲゴザジズゼゾダヂヅデドバビブベボパピプペポヴ.txt" (By NFC) there will be no problem with BOX Drive.
But, with macOS X / Box Drive, the inside of the BOX server is not displayed in the Finder.
"がぎぐげござじずぜぞだぢづでどばびぶべぼぱぴぷぺぽガギグゲゴザジズゼゾダヂヅデドバビブベボパピプペポヴ.txt"(By NFC) uses only 55 characters in NFC.
Are you having another problem?-Operation on mac OSX-
When writing to a FAT32 formatted USB memory device on mac OSX, write the file name using NFC.When uploading data to a shared folder using the cifs protocol on mac OSX, write the file name in NFC format.
When uploading data to a shared folder using the AFP protocol on mac OSX, write the file name in NFC format.
On mac OSX, write file name in NFD format only when writing data to HFS+ format HDD.
mac OSX does not accept any NFC on HFS+, and NFC automatically converts to NFD when downloading data from the BOX server.
-Proposal-
When writing data to the BOX server using BOX Drive for MacOS, please convert it to NFC instead of NFD and write the data.When uploading to the BOX server, no one will be troubled even if it is converted to NFC instead of NFD and saved. Inconvenience has occurred rather than being saved as NFD.
-Additional explanation-
mark of a voiced sound in speech characters is below.
がぎぐげご
ざじずぜぞ
だぢづでど
ばびぶべぼ
ぱぴぷぺぽ
ガギグゲゴ
ザジズゼゾ
ダヂヅデド
バビブベボ
パピプペポヴ
by NFC
がぎぐげご
ざじずぜぞ
だぢづでど
ばびぶべぼ
ぱぴぷぺぽ
ガギグゲゴ
ザジズゼゾ
ダヂヅデド
バビブベボ
パピプペポヴ
by NFD
I want Japanese mark of a voiced sound in speech characters to be unified with NFC.
-Overview-
example: the 'ga' syllabary series in the Japanese alphabet
'ガ'is U+30AC on windows or unix/linux
-> NFC(Normalization Form Canonical Compression)
'ガ'is U+30AB U+3099U on mac OSX
-> NFD(Normalization Form Canonical Decompression)As you know, mac OSX use only NFD.
Windows use NFC usually, but NFD can be used at the same time.When trying to share BOX folder between Win and mac, Inconvenience occurs.
-problem-
First
In Windows explorer, NFC and NFD are displayed as the same character on the screen, so they…2 votes
9875 results found
-
Ability to log and review user-entered prompts in Box AI
After deploying Box AI to users, it would be very helpful to have the ability to log and review the prompts that users enter.
This would support security and compliance needs, such as detecting potential malicious usage and enabling proper auditing when required.Since Box is a platform where sensitive and confidential information is often stored, having this capability is important for safely leveraging AI features.
53 votes -
The ability to search by creator when searching workflows in the “Relay” section of the management console
The administrator will check whether there are any problems with the workflow settings owned by each user, and if there are any problems, they may discuss with the user what needs to be corrected.
Currently, workflows can be searched by name, but users cannot view a list of workflows they individually maintain, which lacks convenience.
Searching by workflow creator improves work efficiency.管理者では各ユーザー毎の所有するワークフローの設定に問題がないか確認のうえ、問題があればユーザーと一緒に修正箇所を議論することがあります。
現在はワークフローの名称で検索か可能となっていますが、各ユーザー毎に保持しているワークフロー一覧を出すことができず利便性に欠けます。
ワークフローの作成者単位で検索できることで作業の効率化が上がります。19 votes -
Past password changes included in the report.
Currently, it is possible to check the date and time of the last password change, but we have confirmed that past password change history is not included in the report.
Being able to check how frequently passwords are changed will also help improve security.現在、最後にパスワード変更した日時を確認することは可能ですがこれまでに変更された実績がレポートに載らないことを確認してます。
どれくらいの頻度で変更されているのか確認できることでセキュリティ向上にも繋がります。14 votes -
We want to apply classification labels using Automate without granting Editors permission to change labels
In Relay, we had a workflow where users would manually trigger a workflow, assign an approval task, and upon approval, automatically change or assign a classification label. This was done to assign a label indicating that the content is ready for public release, enabling external sharing.
However, this cannot be achieved with Automate workflows. Upon checking the specifications, we found that unless the Admin Console allows Editors to modify classification labels, Automate workflows cannot assign labels. In our organization, we have only permitted Co-owners and Owners to change labels. If we allow Editors to change labels, general employees would be able to change labels freely, which we want to avoid.
Since this was achievable in Relay, please make Automate have the same specifications as Relay.Japanese follows
Relayを使い、ユーザーが手動でワークフローを起動し、承認タスクを付与し、承認されたら自動的に分類ラベルを変更する、または付与するという運用をしていた。承認を経て公開可能なラベルを付与して、社外公開を可能にするためです。しかし、Automateのワークフローではそれが実現できません。仕様を確認したところ、管理コンソールで、分類ラベルの変更をEditorに対して許可していないと、Automateのワークフローではラベルを付与できないとのこと。共同所有者＆所有者のみラベル変更を弊社では許可しています。編集者にラベル変更を許可すると、一般の社員も勝手にラベル変更ができてしまうため、それは行いたくないです。従来Relayで実現できていたので、AutomateもRelayと同じような仕様にしてくださいIn Relay, we had a workflow where users would manually trigger a workflow, assign an approval task, and upon approval, automatically change or assign a classification label. This was done to assign a label indicating that the content is ready for public release, enabling external sharing.
However, this cannot be achieved with Automate workflows. Upon checking the specifications, we found that unless the Admin Console allows Editors to modify classification labels, Automate workflows cannot assign labels. In our organization, we have only permitted Co-owners and Owners to change labels. If we allow Editors to change labels, general employees would be…
5 votes -
Request for Improvement of the “People with the Link” Feature in Box
Request for Improvement of the “People with the Link” Feature in Box
We would like to request the following improvements to the “People with the link” option within Box’s Share Link feature, which is used to grant viewing or downloading access to folders or files for organisations or email addresses that do not have a Box account or existing folder permissions.
At present, requiring the link creator to manually set a password is rather cumbersome, and as a result, many users choose not to do so. Since there is no enforcement mechanism, some organisations restrict or even prohibit the use of this feature due to concerns over security management.
Furthermore, when compared with other file transfer services, the People with the link option provides somewhat limited functionality for securely sharing files with users or organisations that do not have a Box subscription. Consequently, some organisations opt to use existing external file transfer services instead of relying on the People with the link feature.
For these reasons, we would like to propose the implementation of the following enhancements.
- Enable password protection for the “People with the link” option. ※No further action should be required from the user.
- The generated “People with the link” URL can then be sent to the recipient via email or other means.
- When the recipient accesses the link, they are prompted to enter their email address in order to receive the password.
- The recipient receives the password notification via email and enters it on the access page.
- After entering the password, the recipient is granted permission to view and download the file.
By providing the above functionality, it would become possible—through administrative console activity logs—to identify, via email address, who accessed or downloaded files shared through the “People with the link” option and when.
This would enable organisations to verify that files have not been downloaded by unintended recipients, thereby strengthening overall information security management.
＜日本語＞
共有リンク機能にて「リンクを知っている全員」を設定し、パスワード設定を有効化した場合の機能改善を提案します。本来、「リンクを知っている全員」はBoxのアカウント持たない組織または人達にファイル送信する際に利用され、ファイル転送サービスの代替方法として活用を提案するものです。
しかしながら、「リンクを知っている全員」のパスワード設定は、共有リンクを作成した本人がパスワードを任意で設定する必要がありとても操作が煩雑です。
また、パスワードを設定したとしても別のメールで連絡をしなくてはなりません。
更に、送信した相手が本当に参照したのか、ダウンロードをしたのか知る方法もないためセキュリティの観点から、ファイル転送サービスを利用した方が安全にファイル送信できると判断し、利用を禁止している組織も多いはずです。そのため以下のような機能を提供するのが良いと考えています。
１．「リンクを知っている全員」を設定。パスワードの有効化を設定。
※ユーザーの操作はここまで２．上記で生成された共有リンクのURLをメール等で相手に送信
３．メール受信者は、共有リンクにアクセスするとパスワードを送信するためメールアドレスの入力が求められる。
４．メールアドレスを入力すると、入力したメールアドレスにパスワードが送信される。
５．受信したパスワードを入力するとファイルを参照またはダウンロードできるようになる。
上記の機能を提供することで、「リンクで知っている全員」でファイルを送信したとしても、入力されたメールアドレスをログで確認できるようにすることで、いつ誰がファイルを参照しダウンロードしたのか管理コンソールのレポート機能で確認できるようにすることで、意図しない相手がダウンロードしていないかチェックすることも可能となり、組織全体のセキュリティ強化に繋がると考えます。
Request for Improvement of the “People with the Link” Feature in Box
We would like to request the following improvements to the “People with the link” option within Box’s Share Link feature, which is used to grant viewing or downloading access to folders or files for organisations or email addresses that do not have a Box account or existing folder permissions.
At present, requiring the link creator to manually set a password is rather cumbersome, and as a result, many users choose not to do so. Since there is no enforcement mechanism, some organisations restrict or even prohibit the use…
19 votes -
Dynamic approving
Customer has a workflow which requires 2 out of 3 stakeholders to approve a document before it progresses. Asking the product team to provide dynamic approval so, for example, when one stakeholder approves a document, the the workflow progresses to require one of the remaining assignees to approve the document.
5 votes -
Global filter
Box APPs would benefit from a global filter (a filter on the APP's main page). This filter would allow to see the dashboard in context:
Projects. The app displays all projects, but allows you to drill into individual projects.
Manufacturing: see an overview of all machines and a global status, but allowing to dive into any machine.
HR: getting an overview of how your hiring is doing globally, while also being able to look at individual countries / cities (multiple fields).
The way APPs is organised right now we have to create an APP for each of these views, making it hard to actually keep an overview and introducing a lot of issues when we need to update the dashboards.
Box APPs would benefit from a global filter (a filter on the APP's main page). This filter would allow to see the dashboard in context:
Projects. The app displays all projects, but allows you to drill into individual projects.
Manufacturing: see an overview of all machines and a global status, but allowing to dive into any machine.
HR: getting an overview of how your hiring is doing globally, while also being able to look at individual countries / cities (multiple fields).
The way APPs is organised right now we have to create an APP for each of these views, making…
5 votes -
Enable Image Pasting in Box Hubs
Box Hubs is a convenient feature, but we would like to further enhance its visual aspect.
We would like to be able to paste images directly into the Hub.Box Hubsは便利な機能ですが、よりビジュアル面を向上させたいです。
Hubの画面に画像を張り付けできるようにしてほしいです。9 votesWe are working on this feature. Please let your manager know if you want to participate in Private Beta or write to box-hubs-beta@box.com
-
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:- View all prompt libraries available to the tenant.
- Choose which prompt libraries are displayed to users.
- Hide prompt libraries that are not relevant or not approved for organizational use.
- Optionally configure visibility by user group, department, or role.
- 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活用を開始できます。一方で、エンタープライズ環境では、すべてのプロンプトライブラリがすべてのテナント、部門、業務プロセスに適しているとは限りません。管理者として、組織の方針や利用目的に合わせて、ユーザーに表示するプロンプトライブラリと表示しないプロンプトライブラリを選択できる必要があります。現状のままでは、業務に関係のないプロンプトや、社内ポリシーに沿わない可能性のあるプロンプトが一覧に表示され、ユーザーの混乱や誤った利用につながる懸念があります。
▼要望内容
プロンプトライブラリについて、管理者がテナント単位で以下を設定できるようにしてほしいです。- テナントで利用可能なプロンプトライブラリの一覧を管理者が確認できる。
- ユーザーに表示するプロンプトライブラリを選択できる。
- 組織で利用しない、または承認していないプロンプトライブラリを非表示にできる。
- 可能であれば、ユーザーグループ、部門、ロール単位で表示対象を制御できる。 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:- View all…
6 votes -
AI-Powered Confirmation Before Adding Collaborators/Sending Links
I’d like Box to add an AI-powered confirmation step when users invite collaborators to a file or folder or send shared links to other users. The AI would quickly scan the content, detect PII or sensitive information, understand the context, and check whether the invited collaborator seems appropriate (e.g., external domain, personal email, unrelated teammate). If something looks unusual, Box would display a confirmation prompt asking the user to verify the invitation. This would help prevent accidental oversharing and reduce security risks caused by human error, while still keeping the collaboration workflow smooth.
16 votes -
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の設定」を変更した際、セキュリティログに記録してほしいです。
コラボレーションや共有リンクに制限をかけていても、何らかの理由でその制限が外れてしまった場合、現状では経緯を追跡する手段がありません。セキュリティやコンプライアンスの観点から、これらの操作履歴を確認できないことは、非常に大きなリスクです。6 votes -
Ability to specify who will be notified when a password is changed.
As part of security operational reviews, administrators may occasionally check whether passwords have been changed multiple times within the same day, when necessary.
Currently, I believe password change notifications are sent to users with administrative privileges, including group administrators.
For operational reasons, we would like group administrators not to receive these notifications, so we would like to be able to optionally configure the recipients of password change notifications.セキュリティ面の運用見直しの一環で、管理者で同日内に何度もパスワード変更していないか等を必要な時にチェック行うことがあります。
現状、グループ管理者含めた管理者権限のあるユーザー宛にパスワード変更通知が届くと思います。
運用上の理由からグループ管理者がこれらの通知を受け取らないようにしたいため、任意でパスワード変更通知先を設定できるようにしたいです。13 votes -
I would like Box Sign to have more flexible permission settings.
When Box Sign is enabled for a user, he/she can send sign requests, check the contents of requests shared with them, and view their inbox.
However, there are users for whom I do not want to allow sending sign requests, but I do want them to be able to check their inbox.For example, our executives who frequently approve or sign documents in Box Sign but do not need to send signature requests by themselves.
I believe it is a potential security risk to give users the authority to send signature requests even though they do not need it.Currently, Box Sign does not have a function to control external Sign sending. It would be great if we could have more granular control, such as allowing users to view the Sign inbox but not send requests.
After signing, users can download and review the signed document and signature log via the sign completion email.
But searching through the email inbox for them is inconvenient, so I would like to be able to complete everything within Box. So want to allow users to check the past signed document in Box via inbox of Box sign.I understand that with Shield access policies it is possible to restrict Box Sign request sending both internally and externally. However, since Box Sign may also be used for internal approval processes, I think making it completely impossible to send is too much.
When Box Sign is enabled for a user, he/she can send sign requests, check the contents of requests shared with them, and view their inbox.
However, there are users for whom I do not want to allow sending sign requests, but I do want them to be able to check their inbox.For example, our executives who frequently approve or sign documents in Box Sign but do not need to send signature requests by themselves.
I believe it is a potential security risk to give users the authority to send signature requests even though they do not need it.Currently,…
28 votes -
Box Drive Cloud Files: Selecting the Cache Storage
With the release of Box Drive Cloud Files, the specification for where the Box Drive cache is stored has been changed:
Traditional Box Drive: C:\Users<USERNAME>\AppData\Local\Box\Box\cache
Box Drive Cloud Files: Same folder as Box Drive
In our company, we have changed the Box Drive mount location and are operating with a reduced capacity on that mounted drive. Due to the above specification change, upload errors caused by insufficient space are occurring.
It is not realistically possible to re-image all corporate users’ PCs and change their storage capacities. A forced migration to Box Drive Cloud Files would therefore impact all users in our organization and could potentially lead to a decline in Box usage.
We strongly request the addition of a feature in Box Drive Cloud Files that allows us to select the cache storage location on the C drive, as was possible with the previous specification.
[Box Drive Cloud Files：キャッシュ保存先の選択]
Box Drive Cloud Filesのリリースにより、Box Driveのキャッシュの保存先が仕様変更されました。
・従来のBox Drive：C:\Users<USERNAME>\AppData\Local\Box\Box\cache
・Box Drive Cloud Files：Box Driveと同じフォルダ内社内ではBox Driveのマウント先を変更しており、マウント先の容量を少なくして運用しています。
上記の仕様変更の影響で、容量不足によるアップロードエラーが発生しています。
社内のユーザーすべてのPCで再キッティングと容量変更をすることは現実的に不可能となり、
Box Drive Cloud Filesへの強制移行は社内のすべてのユーザーに影響が出るため、Boxの利用率低下につながりかねません。従来の仕様と同じように、Box Drive Cloud Filesでもキャッシュの保存先をCドライブに選択できる機能の追加を強く要望します。
With the release of Box Drive Cloud Files, the specification for where the Box Drive cache is stored has been changed:
Traditional Box Drive: C:\Users<USERNAME>\AppData\Local\Box\Box\cache
Box Drive Cloud Files: Same folder as Box Drive
In our company, we have changed the Box Drive mount location and are operating with a reduced capacity on that mounted drive. Due to the above specification change, upload errors caused by insufficient space are occurring.
It is not realistically possible to re-image all corporate users’ PCs and change their storage capacities. A forced migration to Box Drive Cloud Files would therefore impact all users in…8 votes -
Regarding the time it takes for scheduled reports to be generated
Content: The Box support site mentions that report generation can take up to 12 hours.
Most reports are usually generated within a few minutes to a few tens of minutes, but scheduled reports often take about 12 hours to be output.
Although it is within the expected range, waiting half a day for the output affects business operations, so we request a functional improvement to shorten the time it takes for reports to be generated.(日本語)
件名：スケジュールされたレポートが出力されるまでの時間について
内容：Boxサポートサイトにレポートの生成には最大で12時間かかる場合があると記載されております。
ほどんどのレポートは数分から数十分程で出力されることが多いですが、スケジュールされたレポートの場合出力されるまでに12時間程かかることがとても多いです。
範囲内ですが、出力までに半日かかるのは業務に影響がある為、レポート出力されるまでの時間帯を短縮されるよう機能改善要望をします。29 votes -
I want to save Copilot for Microsoft 365-generated content directly to Box
Currently, when I use Copilot’s generative AI features, the only default save destination is OneDrive—Box isn’t even an option. For those of us who live and breathe Box it would be fantastic if we could save Copilot-generated content directly to Box and keep everything in one place.
Right now, every time Copilot asks, “Save to OneDrive?” I feel like saying, “Nice try, Copilot, but my heart belongs to Box!” Please help us Box fans avoid this daily heartbreak and make Box a first-class citizen for Copilot saves. Thank you!
〈Copilot for Microsoft 365で生成したコンテンツを直接Boxに保存したい〉
現在、Copilotで生成AI機能を利用し作成したコンテンツの保存先は、OneDriveがデフォルトとなっており、Boxを選択することができません。
Boxでコンテンツを一元管理するため、Copilotで生成したコンテンツの保存先にBoxを追加してほしいです。23 votes -
IP Address Restriction for Webapp and SELECTED API calls
We want to enable IP address restrictions only for the web app and selected applications.
Possible methods include submitting a list of client IDs exempt from restrictions during application, or providing a UI to specify an app list excluded from IP address restrictions.Currently, only the following two options are available.
- Enable only for Webapp
- Enable for Webapp and All API callsWhat we truly want is to apply IP address restrictions to the web app and BoxDrive. However, selecting “All APIs” renders nearly all other cloud-based integration apps unusable.
For example, losing integrations that significantly boost productivity—like Salesforce, Zoom, or Box connectors for Zapier and n8n—is a major issue. While we could ask providers for their IP addresses and allowlist them all, maintaining a list of potentially changing IP addresses is impossible.
Box itself recommends setting rules by domain in its firewall configuration support article, acknowledging IP addresses can change.The reason IP address restrictions via SSO cannot solve this is that they cannot prevent scenarios where employees authenticate internally, then take their device outside and access the company Box from an unspecified access point. Box's own IP address restrictions are powerful because they can prevent this, and it is essential to configure them to work alongside various integrations.
We want to enable IP address restrictions only for the web app and selected applications.
Possible methods include submitting a list of client IDs exempt from restrictions during application, or providing a UI to specify an app list excluded from IP address restrictions.Currently, only the following two options are available.
- Enable only for Webapp
- Enable for Webapp and All API callsWhat we truly want is to apply IP address restrictions to the web app and BoxDrive. However, selecting “All APIs” renders nearly all other cloud-based integration apps unusable.
For example, losing integrations that significantly boost productivity—like…21 votes -
AI restriction in shield access policy
Shield Access Policy Settings to include the possibility to restrict the use of AI on content. That would prevent using AI on files containing PII, or other files including sensitive content in particular when using Box AI in Box Hubs.
18 votes -
Reference loop variables in a conditional branch within the loop in Box Automate workflow
In a Box Automate workflow, when looping through files, we need to be able to run conditional checks on values/properties of the file within that loop.
Potential use case: a user may want the workflow to ignore certain file types, or to only run Box AI Agent operations on certain files.
Currently, many variables can be referenced within the "conditional split" element within a "loop" element, but not the loop variables themselves.
4 votes -
Allow a table in Box Forms
Allow a table in Box Forms to make entry easier for end users with copying and pasting
6 votes
- Don't see your idea?