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
9664 results found
-
Only folder owners and co-owners can send collaborator invites and add this folder to a Hub
In the Box Support article: https://support.box.com/hc/en-us/articles/25870093558675-Adding-Content-to-Box-Hubs, it says this checkbox reads "Only folder owners and co-owners can send collaborator invites and add this folder to a Hub"
The actual setting in Box only says "Only folder owners and co-owners can send collaborator invites" leaving out the part about Box Hubs, this needs to be updated.
This also relates to: https://pulse.box.com/forums/909778-help-shape-the-future-of-box/suggestions/48513617-unable-to-add-a-content-to-a-hub-site-due-to-folde where this setting really makes no sense as inviting collaborators really has nothing to do with attaching files and folders into a Box Hub.
1 vote -
playback speed controls for audio or video files
At the moment, the Box Mobile app for iPad doesn’t include playback speed controls for audio or video files, so I suggest to add this function. The web already has this function. It would enhance the audio user playback!
1 vote -
I want to ensure that clients cannot forward links that I send with intellectual property. When clients/customers order my products, I want
I want to ensure that clients cannot forward links that I send with intellectual property. When clients/customers order my products, I want them to have a downloadable link (without having a box account) to access the document(s). I do not want to send a passcode for access (unless it is required).
I tested out this feature with a few of my email accounts not linked to my Box account. I also tested it out with a Box user in with account access, but to an email not linked to Box.
1 vote -
Way to close any open editing sessions.
It would be beneficial to have a way to close any open editing sessions.
We have run into this issue multiple times where sessions are stuck open, and folks are unable to remove or edit documents, do to this issue.
3 votes -
Feature Request – Enable "Favorites" Feature on Box Drive
The 'Favorites' feature in Box allows users to quickly access frequently used files and folders by marking them as favorites. However, adding folders to 'Favorites' is only available through the Box web app and is not supported on Box Drive, the desktop application.
5 votes -
Box integration sending emails with inconsistent formatting
Box integration is sending unusal format to emails resulting in + between each word. This was reported and found Thanks for testing and sharing your observations. The behavior you’re seeing with the + signs in the subject and body is due to how the Box integration generates the Outlook on the web compose window. It URL-encodes spaces as +, which Outlook sometimes displays as spaces and sometimes shows literally — this explains why clearing the browser cache makes it look correct for the first attachment but not for subsequent ones.
Essentially, this is a limitation of how the integration constructs the subject and body text, not an issue with your browser or Outlook on the web itself. Cache-clearing temporarily loads a fresh script that behaves slightly differently, but it doesn’t fully change the underlying encoding behavior.
At present, there isn’t a reliable client-side fix. The only way to consistently get properly formatted subjects and links would be for the integration to generate the email body and subject using HTML or encoding via Microsoft’s Graph API rather than plain URL-encoded text
Box integration is sending unusal format to emails resulting in + between each word. This was reported and found Thanks for testing and sharing your observations. The behavior you’re seeing with the + signs in the subject and body is due to how the Box integration generates the Outlook on the web compose window. It URL-encodes spaces as +, which Outlook sometimes displays as spaces and sometimes shows literally — this explains why clearing the browser cache makes it look correct for the first attachment but not for subsequent ones.
Essentially, this is a limitation of how the integration constructs…
1 vote -
selecting a date on a file request page for mobile
When I send a file request on Mobile page, it's difficult to select a correct date that I hope from a metadata template . I can not see the whole of the calender and it doesn't follow my touch action on the mobile screen.
2 votes -
I would love if we could Embed AI Agents, and assign specific AI Agents to specific Hubs.
Hi there! I'm trying to make the power of Box AI accessible to my users. Right now the best thing would be to give them a chatbot to read HR documents, on our Intranet in Sharepoint.
I would love to be able to embed ONLY the Agent into Sharepoint, but so far we can only embed the Box Hub. Therefore if my user wants to ask about their HR benifits, my user has to:
1. Go to the HR Sharepoint Site (where they normally find info on employee benefits, etc.)
2. Unlock the blue/white Box Cloud image (see: "RC HR Screenshot 0 - Embedded into Sharepoint.png")
3. Read my instructions on the hub, ignore the folders in the hub, and click the Box AI button (see: "RC HR Screenshot 1 - user reads instructions.png")
4. Change the Default AI Agent (see: "RC HR Screenshot 2 - default AI Agent.png")
5. The user has to somehow know that they're using the default AI agent, and they need to use the dropdown to the proper HR Agent "HeberBot" (see: RC HR Screenshot 3 - Dropdown to proper Agent.png)
6. then finally type their question.I would love for this to be simplified somehow. Can you suggest other ways, or let me know if there's something that box has planned to simplify this? The best outcome would be: I would love for my user to go to the HR site, and type questions to the correct AI Agent.
So I guess this request can be broken down to 2 technical asks:
1. Embed Box AI Agents/chatboxes directly into sharepoint.
2. Allow admins to assign specific AI Agents to specific Box Hubs. ( For example, my HR agent to my HR document hub. And inherantly disallow the default Box AI agent, or other AI Agents)Hi there! I'm trying to make the power of Box AI accessible to my users. Right now the best thing would be to give them a chatbot to read HR documents, on our Intranet in Sharepoint.
I would love to be able to embed ONLY the Agent into Sharepoint, but so far we can only embed the Box Hub. Therefore if my user wants to ask about their HR benifits, my user has to:
1. Go to the HR Sharepoint Site (where they normally find info on employee benefits, etc.)
2. Unlock the blue/white Box Cloud image (see: "RC HR…5 votes -
Allow Multiple Enterprise IDs (EIDs) to be Defined as a Single Internal Organization (Tenant Federation)
For security or operational reasons, it is common for a single enterprise to operate multiple Box tenants. However, when an organization's internal user scope ("company") is defined by its Enterprise ID (EID), users from these separate-but-related tenants are treated as external collaborators.
This creates significant problems and reduces usability:
Shared Link Restrictions: Users from a related tenant cannot access links shared with the "People in your company" permission level.
Group Collaboration Issues: It is not possible to invite groups from a related tenant to collaborate on content.
Reduced Security and Convenience: Collaborators from related tenants are flagged as "external," which can trigger stricter security policies (e.g., via Box Shield) and create unnecessary friction for users who are, in reality, internal employees.
These limitations force administrators to use less secure sharing methods or manage a complex web of individual invitations, undermining the benefits of having separate tenants in the first place.
Proposed Solution
Develop a feature that allows administrators to designate other specific Enterprise IDs as part of their internal organization.This "Tenant Federation" or "Trusted EID List" would enable all users across the federated tenants to be treated as a single "company." By implementing this, the following would be possible:
Users from trusted tenants could seamlessly access "People in your company" shared links.
Collaboration invitations could be extended to user groups across all federated tenants.
Security and governance policies (like those in Box Shield) could be applied consistently to all users within the true organizational boundary, removing the "external collaborator" status for trusted colleagues.
This would provide a secure and efficient way to manage collaboration across the complex structures of modern enterprises.
For security or operational reasons, it is common for a single enterprise to operate multiple Box tenants. However, when an organization's internal user scope ("company") is defined by its Enterprise ID (EID), users from these separate-but-related tenants are treated as external collaborators.
This creates significant problems and reduces usability:
Shared Link Restrictions: Users from a related tenant cannot access links shared with the "People in your company" permission level.
Group Collaboration Issues: It is not possible to invite groups from a related tenant to collaborate on content.
Reduced Security and Convenience: Collaborators from related tenants are flagged as "external," which…
1 vote -
Allow Custom Domain Email Addresses for Service Accounts and App Users
Service Accounts and App Users are automatically assigned an email address with the @boxdevedition.com domain. This becomes problematic when a company's collaboration settings define internal users by their own corporate domain (e.g., example.com).
Under this configuration, if a shared link's access level is set to "People in your company," the Service Accounts and App Users are treated as external users because their @boxdevedition.com email does not match the company's domain. Consequently, they are blocked from accessing these internal-only links, which hinders automated workflows and API-based processes.
Proposed Solution
Introduce a feature that allows administrators to change the assigned @boxdevedition.com email address for Service Accounts and App Users to an email address under a domain owned and verified by their company.By enabling this change, these accounts would be correctly identified as internal users within the tenant. This would ensure they can successfully access shared links restricted to "People in your company," allowing for seamless and secure integration with internal automated processes.
Service Accounts and App Users are automatically assigned an email address with the @boxdevedition.com domain. This becomes problematic when a company's collaboration settings define internal users by their own corporate domain (e.g., example.com).
Under this configuration, if a shared link's access level is set to "People in your company," the Service Accounts and App Users are treated as external users because their @boxdevedition.com email does not match the company's domain. Consequently, they are blocked from accessing these internal-only links, which hinders automated workflows and API-based processes.
Proposed Solution
Introduce a feature that allows administrators to change the assigned @boxdevedition.com email…1 vote -
Request for control over shared links for company users
In order to share content quickly and securely with certain company users, we would like to request the following features
・Allow passwords to be set on shared links even when they are addressed to company users.
・Allow tenant default values for shared link expiration to be configured specifically for “company users.”
【In Japanese】
＜タイトル＞
会社ユーザー向け共有リンクの制御についての要望＜本文＞
会社のユーザーの一部に対して高速かつ安全にコンテンツを共有するため、以下の機能を希望します。・会社のユーザー宛の共有リンクにもパスワードを設定できるようにしてほしい。
・共有リンクの有効期限のデフォルト設定について、「会社のユーザー」に限定したテナントデフォルト値を設定できるようにしてほしい。
1 vote -
Please eliminate the need to log in and out when updating the app
When updating the app or fixing issues, we would like to avoid requiring users to log in and out whenever possible. For administrators, it is burdensome to notify employees about changes that need to be reflected.
1 vote -
Hubs - Add ability to arrange sections horizontally
Will there eventually be an opportunity to arrange sections horizontally in the future? Thinking more like a canvas for a dashboard.
29 votes -
Ability to create private subfolders in Parent folders, and limit Parent-level collaborators from accessing the private subfolder.
Ability to create private subfolders in Parent folders, and limit Parent-level collaborators from accessing the private subfolder. Only added collaborators should be able to work in that subfolder.
3 votes -
Add a variable to assign a unique number when renaming a file with BoxRelay
I would like you to add a variable that allows the signed file to be given a numbered name when multiple people sign the same file by setting up a Relay triggered by Box Sign.
-in Japanese-
Box SignをトリガーにRelayを組んで複数人が同じファイルに署名した場合に、署名したファイルに採番した名前を付けられるような変数を追加してほしい。2 votes -
Box Shield: "Read Only" Security Control setting
In Box Shield, add a Security Control setting that locks the folder and effectively puts the folder in a read-only mode, disallowing edits and uploads, no matter what the collaborators' permission levels are (except Admin, obviously).
This way, it's possible to give users a "lower" permission level to a subfolder without affecting their elevated permissions in the parent folder.
3 votes -
Bulk Change Collaborator Permissions
We have folders that collaborate hundreds of users. We have occasion to need to modify their permissions. It would be very useful if there was a way to modify the permission level of multiple users. Using the Web UI to modify a single user at a time is very inefficient.
Either via selecting multiple users at a time, or even better, if you were to "re-invite" a user to a folder and select a different collaboration permission.
This way you could use the invite dialog box to re-invite 100 users - and change their permissions all at once.2 votes -
Support DocuWorks(.xdw) for opening
I often use DocuWorks(.xdw) files, so I'd like to be able to open them directly from the Box browser.
-in Japanese-
DocuWorks(.xdw) のファイルを利用する機会が多いため、Boxのブラウザ上から直接開けるようにしてほしい。6 votes -
Expire shared links for external users, but not internal employees
When employees use shared links to exchange sensitive data with clients, we set them to expire for security reasons. However, when we later encounter a shared link within an internal email or slack message, we can no longer see what it linked to. We could go run a report to find out, but that would be a support ticket. It would be much better if shared links could just continue working for employees (if they are permitted direct access) even after they have expired for external users.
Before link expiration, content is accessible to anybody internal or external who has the link - if that's how the link was set up.
After link expiration, content would still be accessible to internal users only if they already have access to the content. So after link expiration, no additional access is granted - just the ability to access something using an expired link as well as at its regular URL.
If an employee has access to content, for us there is normally for us no reason that they should not be able to access that content via an expired shared link if they are logged in.
This should be a setting in "Shared Link Settings" dialog.
Also in Enterprise settings, Content & Sharing->Auto-Expiration ability to control a default of on or off for this feature.Related, but insufficient for this use case:
- 35982223-shared-link-lookup-tool
- 36107317-separate-shared-links-for-internal-and-external-us
- 49706036-expired-shared-link-lookup-for-admins
- 48809945-decode-expired-box-links
- 35982223-shared-link-lookup-toolWhen employees use shared links to exchange sensitive data with clients, we set them to expire for security reasons. However, when we later encounter a shared link within an internal email or slack message, we can no longer see what it linked to. We could go run a report to find out, but that would be a support ticket. It would be much better if shared links could just continue working for employees (if they are permitted direct access) even after they have expired for external users.
Before link expiration, content is accessible to anybody internal or external who has…
1 vote -
Envelope support
At present box sign doesn't support envelope feature. Like adobe esign api or docusign api. I can request an agreement or an envelope to a set of users and their sign fields mapped in the entire document .
Box at present considers the signature field per document only. This is an essential piece to complete against adobe esign api or docusign api.
From pricing perspective box can introduce a special pricing for this as well.
1 vote
- Don't see your idea?