669 results found

1. Prefix, Suffix, and related fields in Box Folder Names.

   Let's be honest, at the end of the day, people sign up for Box for cloud space and organization. One very big pain point for my company is the inability to apply related fields and/or prefix/suffix's to our folder names. Let's take a very simple folder structure

   Parent Folder |Folder A, Folder B | Folder A - 1, Folder A - 2, Folder A - 3 |

   Currently, if I wanted to append the {Parent Folder} to each folder within the folder structure, I would have to go and rename each folder individually.

   This idea thread would solve this problem. This solution would give the user the power to Apply a prefix or a suffix to a folder structure. It would be awesome if we could use API fields such as {Created Date} or {Parent Folder} as examples. Additionally, the user should be able to apply just plain text. For example, As a user, if I want to append ABCDEF - (original folder/file name) then I should be able to do this.

   This idea comes from a real life situation where a much more complex folder structure was templated out and all 50 folders for 25 entities had to be renamed individually because of the inability to simply apply a suffix or prefix in Box. Please upvote and prioritize this idea!

   Let's be honest, at the end of the day, people sign up for Box for cloud space and organization. One very big pain point for my company is the inability to apply related fields and/or prefix/suffix's to our folder names. Let's take a very simple folder structure

   Parent Folder |Folder A, Folder B | Folder A - 1, Folder A - 2, Folder A - 3 |

   Currently, if I wanted to append the {Parent Folder} to each folder within the folder structure, I would have to go and rename each folder individually.

   This idea thread would solve this problem.… 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 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. Invite all users who have sent an email to the email address associated with the folder

   currently, Co-admins are manually inviting users to folders.
   Inviting is generated for the number of projects, it takes man-hours each time, so we want to make it easy to invite.

   For example, we would like to have a mechanism that can invite all users who have sent an email to the email address associated with the folder.

   [How to use]
   Generate an email address associated with the folder
   (It is assumed to be something like an email address for uploading emails)
   Give this email address to the user we want to invite
   Each user will send an email to this email address
   .User who sent the email will receive an invitation to the folder from Box

   【日本語】
   フォルダに紐づいたメールアドレス宛にメール送信したユーザー全員を招待する機能

   現在、フォルダへのユーザー招待は共同管理者が手動で行っている。
   プロジェクトの数だけ作業が発生するため、毎回工数がかかるため、招待を簡単に行えるようにしたい。

   例えば、フォルダに紐づいたメールアドレス宛にメール送信したユーザーをすべて招待できる仕組みが欲しい。

   【使い方】
   1.フォルダに紐づくメールアドレスを生成します
   　(メールアップロード用のメールアドレスのようなものを想定しています)
   2.招待したいユーザーにこのメールアドレスを教えます
   3.各ユーザーがこのメールアドレスへメールを送信します
   4.メールを送信したユーザーにBoxからフォルダへの招待通知が届きます

   currently, Co-admins are manually inviting users to folders.
   Inviting is generated for the number of projects, it takes man-hours each time, so we want to make it easy to invite.

   For example, we would like to have a mechanism that can invite all users who have sent an email to the email address associated with the folder.

   [How to use]
   Generate an email address associated with the folder
   (It is assumed to be something like an email address for uploading emails)
   Give this email address to the user we want to invite
   Each user will send an email to this… 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  ·  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

3. Move whith leaving a bookmark menu

   【Request】
   I would like to see "Move whith leaving a bookmark" added to the file menu.

   【Background】
   We are trying to centralize data management by using Box, but
   Copying files and folders within Box becomes inefficient if it becomes the norm.
   Searchability is reduced, file merging becomes more time-consuming, and the risk of editing or sending the wrong file increases.

   We want users to use "move" as their main tool, but
   However, if a file is removed from the source folder, other users will be confused and it will be difficult to use.

   The bookmark creation function is difficult to find and is not widely used.
   There are users who understand bookmarks, but they are not used much because of the complicated operation.

   【Expected behavior】
   (1)"Move whith leaving a bookmark" will be displayed in the menu when right-clicking on a file.
   (2)When "Move whith leaving a bookmark" is clicked, a shared link*1 for the target file is automatically issued, and a bookmark with the following information is created in the folder.
   - URL: File URL of the target file (since the shared link may be deleted)
   - Name: {FileName} has been moved
   - Description: {FileName} has been moved to a different folder by {the name of the user who performed the move}. If you do not have access to this bookmark, check with {the name of the user who performed the move}.

   (3)The Move menu will open, and users select the destination and move the file.

   Please consider this idea to realize centralized data management and business efficiency using Box.

   *1 The open range is the one specified as default in the Enterprise settings. The behavior of issuing an open link by default should be avoided at all costs.

   【Request】
   I would like to see "Move whith leaving a bookmark" added to the file menu.

   【Background】
   We are trying to centralize data management by using Box, but
   Copying files and folders within Box becomes inefficient if it becomes the norm.
   Searchability is reduced, file merging becomes more time-consuming, and the risk of editing or sending the wrong file increases.

   We want users to use "move" as their main tool, but
   However, if a file is removed from the source folder, other users will be confused and it will be difficult to use.

   The bookmark creation function is difficult to… 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  ·  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

4. Extend auto collaboration per folders only

   Hi team,

   Submitting this feature request in behalf of user, requesting to add their visibility to extend auto collaboration per specific folders only.

   There's a similar post on this subject, but not exactly the same. We can set an expiration date for external collaborators at the enterprise level, which is essential to security, and should be set as the "default" setting at the enterprise level. However, there are certain circumstances where a folder would need to be shared long term with many people, and the Box owner account should have the ability to do one of two things, or both:

   We know that each collaborator's time can be extended; manually, and individually. In our case, we have 130 external collaborators on one folder, and because they are our customer, we cannot disrupt the workflow, inconvenience them, and let their access expire. The folder owner will need to manually edit access 130 times, on 130 different collaborators, every 60 days to extend their access. That is an unnecessary amount of work, and we cannot compromise our security standards to never let access expire over the entire organization just to accommodate this one folder.

   1.) The Box Owner account, and only the Box owner account, should be able to bypass the Enterprise level setting to customize specific folders. I see the answer on another post is that this need is rare, and adds unwarranted complexity to the system. But, this is not rare; it's a document sharing system, and that's its sole purpose. Even if this functionality were only able to be implemented at the root folder level, that would at least provide a workaround for these instances.

   2.) If the expiration date can't be managed at the folder level, then we should be able to bulk-manage external collaborators on the folder level. I should be able to select all external collaborators on a folder, and extend their access in one action, instead of 130 individual actions. It's difficult enough to need to do this every 60 days, but also having to repeat this 130 times warrants moving to another system to accommodate our needs.”

   Hi team,

   Submitting this feature request in behalf of user, requesting to add their visibility to extend auto collaboration per specific folders only.

   There's a similar post on this subject, but not exactly the same. We can set an expiration date for external collaborators at the enterprise level, which is essential to security, and should be set as the "default" setting at the enterprise level. However, there are certain circumstances where a folder would need to be shared long term with many people, and the Box owner account should have the ability to do one of two things, or both:

   … 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  ·  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. Fix missing Access-Control-Allow-Origin header for CORS 401 requests

   This relates to the upload files API endpoint (https://developer.box.com/reference/post-files-content/) but likely applies to other endpoints as well.

   When making a call to the above endpoint via CORS, you provide a Bearer token to the request. This token is used to identify the box account to make the request on behalf of, which is then used to return an Access-Control-Allow-Origins header configured to that box account's CORS whitelisted domains.

   In the case of a successful request to the above endpoint, the OPTIONS preflight request returns the Access-Control-Allow-Origin header with the request origin set. The actual POST request then returns a 201 with Access-Control-Allow-Origin: *.

   In the case of a domain mismatch, I assume the Access-Control-Allow-Origin header would not be present on the POST request, causing a CORS failure.
    
   However, if the token has expired or is otherwise invalid, the API cannot identify which Box account to run as. The OPTIONS request still returns the requesting origin as the Access-Control-Allow-Origin header, however, the POST request returns a 401 status but no Access-Control-Allow-Origin header.

   I assume the above is because the valid token is used to identify whether the CORS request is from a valid domain. The consequence of this is that browser CORS protection kicks in, and the resulting 401 error cannot be read, even though it originated from a valid domain.

   Two proposed solutions:
   1. Allow the requestor to specify the account id (or some other way of identifying the box account) in the request. The app can then use this id instead of the token to determine the appropriate CORS domains. This will, of course, allow unauthenticated requests to trigger a CORS check for a particular account. However, this is standard for CORS. The CORS layer is designed to trigger before other parts of the request.
   2. Always return the Access-Control-Allow-Origin header for 401 requests, either as "*" or as the requestor origin. This of course basically exempts 401 requests from CORS protection, so should likely be only enabled as an optional setting in your box account.

   This relates to the upload files API endpoint (https://developer.box.com/reference/post-files-content/) but likely applies to other endpoints as well.

   When making a call to the above endpoint via CORS, you provide a Bearer token to the request. This token is used to identify the box account to make the request on behalf of, which is then used to return an Access-Control-Allow-Origins header configured to that box account's CORS whitelisted domains.

   In the case of a successful request to the above endpoint, the OPTIONS preflight request returns the Access-Control-Allow-Origin header with the request origin set. The actual POST request then returns… 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  ·  Uploads  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Add "FOLDER.TRASHED" event trigger to Webhooks v2

   The existing event trigger "FOLDER.DELETED" only triggers a notification when a folder is permanently removed (deleted from Trash). Currently, there is no option to receive a webhook notification if a folder is sent to the trash. "FOLDER.MOVE" does not capture this action either.

   0 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

   delivered  ·  0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →

7. generate folder uploaAdd an action to generate an email upload address for a folder in Box Automated email address

   We would like Box Automate to provide a folder action that enables email uploads for a specified folder and generates or retrieves the folder's email upload address.

   Currently, email uploads must be enabled manually in the settings of each folder. This becomes time-consuming when folders are created dynamically or when the same configuration must be applied to many folders.

   For example, we would like to create the following workflow:

   1. Create a new folder through Box Automate.
   2. Enable email uploads for the newly created folder.
   3. Generate or retrieve the folder's email upload address.
   4. Store the email address in metadata, send it through a notification, or use it in a subsequent workflow action.

   It would also be helpful to have an option to restrict email uploads to folder collaborators only.

   Adding this folder action would make it possible to automate processes that collect email attachments in dynamically created Box folders, without requiring users or administrators to manually configure each folder.

   Requested actions:
   - Enable email uploads for a folder
   - Generate or retrieve the folder's email upload address
   - Optionally restrict email uploads to collaborators
   - Make the generated email address available as a variable for subsequent Box Automate actions

   Box Automateのフォルダアクションに、指定したフォルダのメールアップロードを有効化し、アップロード用メールアドレスを生成または取得する項目を追加してほしい。
   取得したメールアドレスは、後続アクションで通知本文やメタデータなどに使用できる変数として利用可能にしてほしい。
   また、フォルダのコラボレータからのメールのみを許可する設定も選択できるようにしてほしい。

   We would like Box Automate to provide a folder action that enables email uploads for a specified folder and generates or retrieves the folder's email upload address.

   Currently, email uploads must be enabled manually in the settings of each folder. This becomes time-consuming when folders are created dynamically or when the same configuration must be applied to many folders.

   For example, we would like to create the following workflow:

   1. Create a new folder through Box Automate.
   2. Enable email uploads for the newly created folder.
   3. Generate or retrieve the folder's email upload address.
   4. Store the email address in metadata, send it… 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

8. Request to improve behavior where updaters are visible only when operating from mobile

   Hi Box Teams,

   I would like to improve the following behavior.

   Problem behavior:
   If non-collaborators access the People with the link from Box's web app, they won't see who updated the file, but if they access it from Box's mobile app, they'll see who updated the file.

   This problem occurs when a folder's co-owner or owner updates a file. If the user has the permission of the editor or lower, the user who updated the file is displayed as "Anonymous".

   Expected Behavior:
   Since we have set the folder so that only the owner or co-owner can see the information, we would like to not show the information of the person who updated the file, even if the access is from an open link, even if the access is from Box web app or mobile app.

   Conditions for creating a problem
   ・The following folder settings are enabled:

   [folder setting]>[Privacy]>[Collaborators]>[Hide callaborators and their activity from non-owners]

   ・A file with a shared link was last modified by the owner or co-owner of the folder.

   ・The scope of shared link disclosure is set in People with the link for files under the folder.

   ・Non-collaborators access the shared link and view it in the Box mobile app.

   Specific steps to reproduce the problem：
   (1)From a mobile device, a user who is not a collaborator accesses a shared link whose disclosure range is People with the link.

   • At this time, if the Box application is not installed, the default web browser changes to the Box mobile site, where file information can be checked, but the name of the person who updated the file is not displayed.

   (2) You will be redirected to the Box app. If you are not logged in, you will be asked to log in, so you have to log in to the Box app.

   (3) Displays the contents of the shared link destination.

   (4) Display "File information" from "..."

   (5) "Update time" and "Updater name" are displayed in the "Change date" item.

   • This problem occurs when a folder's co-owner or owner updates a file. If the permission is less than or equal to the editor, "Anonymous" is displayed.

   I'm sorry to trouble you, but I appreciate your consideration.

   Best

   Hi Box Teams,

   I would like to improve the following behavior.

   Problem behavior:
   If non-collaborators access the People with the link from Box's web app, they won't see who updated the file, but if they access it from Box's mobile app, they'll see who updated the file.

   This problem occurs when a folder's co-owner or owner updates a file. If the user has the permission of the editor or lower, the user who updated the file is displayed as "Anonymous".

   Expected Behavior:
   Since we have set the folder so that only the owner or co-owner can see the information, we… 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  ·  Mobile  ·  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. Add "LINK.CREATED" to Webhooks V2 event trigger
   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 →
   delivered  ·  Aaron Verstraete responded

   https://docs.box.com/reference#event-triggersSHARED_LINK.CREATED

10. Support articles

    Wow, 'Support' is not even an option on the dropdown menu above. Maybe that is the root of the problem.

    Here are FIVE Suggestions:

    1.

    Add 'Support' as an option on the menu above.

    2.
    Folders that I can see via a web browser were not appearing on my desktop. I tried to find a support article. Found this one:

    Box Sync Troubleshooting Basics

    https://community.box.com/t5/Box-Sync-Troubleshooting/Box-Sync-Troubleshooting-Basics/ta-p/82

    It does not address what I eventually figured out to be the problem: For each folder, I have to manually click the button with three little dots, then select from the menu the three little dots + More Actions, then select ‘Sync’

    I only accidentally found that after wasting A LOT of time trying to send my sync report, etc.

    That is a basic issue. It should appear in that article.

    ---

    3.
    At the bottom of the article (and probably all support articles), there is a line of text that says: “Was this article helpful?”
    The options are Yes and No.
    If the person clicks ‘No’ they should be presented with a text box where they can leave a message saying what the problem is. That would let Box get the feedback it needs to improve articles. Just collecting a ‘No’ does not help.

    Also, that text box would let the person submit the suggestion right away, instead of having to dig around to try to find a way to submit it (which many of us will not do) and waiting for the chat.

    ---

    1. I wasted lots of time on chat, just to submit this suggestion.
       

    That chat person wrote, "You can also submit your feedback on this site: https://pulse.box.com/forums/909778-product-feedback"

    That link should be provided here: https://community.box.com/t5/Contact-Support/ct-p/BoxSupport#

    ---

    5.
    Typing in this little box and needing to scroll up and down to see just a few lines at a time is a lousy experience. Every other website in the world lets you drag the corner of the box to make it larger and easier to read. Please do the same.

    Wow, 'Support' is not even an option on the dropdown menu above. Maybe that is the root of the problem.

    Here are FIVE Suggestions:

    1.

    Add 'Support' as an option on the menu above.

    2.
    Folders that I can see via a web browser were not appearing on my desktop. I tried to find a support article. Found this one:

    Box Sync Troubleshooting Basics

    https://community.box.com/t5/Box-Sync-Troubleshooting/Box-Sync-Troubleshooting-Basics/ta-p/82

    It does not address what I eventually figured out to be the problem: For each folder, I have to manually click the button with three little dots, then select from the menu the three little… 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  ·  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

11. Detailed description along with title of “My Collection.”

    We expect to improve work efficiency by making good use of "My Collection".
    However, as "My Collection" grows, we are having a problem where the contents of "My Collection" (the intention behind its creation) cannot be determined from the title information.
    As a result, we will need to open "My Collection" and check the contents, and this has not improved work efficiency at the moment.
    We considered including the purpose of creating the collection in the name of each collection, but this would require us to place the cursor over each title, which would be very inconvenient for checking the titles.

    Request 1
    “Please add the ability to enter and display annotations such as creation intent below the title of "My Collection" on the screen when opening https://app.box.com/collections.
    If it is difficult to show it alongside the title of "My Collection", please make it appear on-cursor.

    Request 2
    Also, please display this note on the screen where we open a specific "My Collection" (e.g. https://app.box.com/collection/1234567).
    The ideal image we have in mind is something that would be displayed like "Folder description."
    Reference: Adding Descriptions to Folders and Files
    https://support.box.com/hc/en-us/articles/360043694654

    ---

    マイコレクションをうまく活用することで業務効率の向上を見込んでいます。
    しかしながら、マイコレクションが増えていく中で、タイトルの情報からではマイコレクションの内容(作成意図)が分からなくなる問題が発生しています。
    そのため、マイコレクションを一度開き、中身を確認する作業が必要となっており、現時点では作業効率が向上していない状況です。

    マイコレクションの名称に作成意図を記載することも検討しましたが、すべてのタイトルに一度カーソルを合わせる必要が発生するため、タイトルの確認を行う上で大変不便です。

    要望①
    " https://app.box.com/collections "を開いた際の画面にて、マイコレクションのタイトルの下に作成意図などの注釈を記入、表示する機能を追加してください。
    もしもマイコレクションのタイトルと併記することが難しい場合は、オンカーソルで表示するようにしてください。

    要望②
    また、特定のマイコレクションを開いた画面 (例： https://app.box.com/collection/1234567 )にもこの注釈が表示してください。
    イメージとしては、フォルダの説明のように表示して欲しいと考えています。

    　参考：フォルダとファイルへの説明の追加
    　https://support.box.com/hc/ja/articles/360043694654

    We expect to improve work efficiency by making good use of "My Collection".
    However, as "My Collection" grows, we are having a problem where the contents of "My Collection" (the intention behind its creation) cannot be determined from the title information.
    As a result, we will need to open "My Collection" and check the contents, and this has not improved work efficiency at the moment.
    We considered including the purpose of creating the collection in the name of each collection, but this would require us to place the cursor over each title, which would be very inconvenient for checking the… 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  ·  Collections  ·  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. Password reset process is cumbersome

    Even with the understanding that my specific situation might add a few steps, it is significantly longer and more involved than the analogous process for any other product, tool, or service that I use. I have described the steps that I have to go through and would encourage the Box Developers and UX Teams to consider a more seamless way to do this in some future release.

    Reset Password – Box Drive
    Key:
    - = optional step, performed for positive validation that the new password was accepted
    + = step that is specific to my setup

    1. At Windows/Domain login, notification appears stating that I am “no longer connected” to Box and should log in again. Note that no indication is given as to why this is, but in practice, I have learned that this means that the password has expired.
    2. 2. I generally log in anyway to confirm this. Logging in generates a prompt for the MFA code, which I obtain and enter. At that point, I am told that my password has expired and I am directed to log in to the web site to reset it.
    3. I log in to the web site. I am again prompted for my MFA code, which I retrieve and enter. I am then notified that my password has expired, and I am asked to enter my email address – the same address that I just used to log in – in order to receive a reset prompt. I do so.
    4. I check my email program for the message and click on the link provided; I am returned to my browser at the Password Reset form/page
    5. At the web site, I enter my new password
    6. 6. I log in to the web site, using my new password, to confirm that it has been accepted and that LastPass has correctly saved the new value. I am again prompted for my MFA code
    7. I log in to the app using my new password and another MFA code
    8. 8. In my specific setup, I then launch my virtual desktop (AWS WorkSpace), which also has Box installed. I see the same “You are not connected to Box” message, but this time I am able to simply log in to the app with my new password. Once more – fifth time – I am prompted for an MFA code

    The entire process takes several minutes, and can take up to ten, depending on optional steps, latency in receiving the email or MFA codes, etc. It requires that I log in to either the app or the web site a minimum of three times, and as many as five in my particular scenario. Honestly, I have an easier time resetting my bank’s online credentials, or reporting that my credit card was lost and getting a new one. As an IT professional myself, I completely understand the need for security, and I appreciate the availability of options in the process, but I am sure that this can be made at least a little less cumbersome. Would you at least take a look at it? Thanks!

    Even with the understanding that my specific situation might add a few steps, it is significantly longer and more involved than the analogous process for any other product, tool, or service that I use. I have described the steps that I have to go through and would encourage the Box Developers and UX Teams to consider a more seamless way to do this in some future release.

    Reset Password – Box Drive
    Key:
    - = optional step, performed for positive validation that the new password was accepted
    + = step that is specific to my setup

    1. At Windows/Domain login, notification… 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  ·  Security  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Case #3631047 - Feature Request: Improve Folder Sorting Persistence and Save As Navigation in Box

    Hello Box Product Team,

    I recently provided feedback and requested an feature enhancement in the box support case "#3631047".

    Thank you for reviewing our feedback. We understand that the current behavior is working as designed and that there are currently no administrative settings or workarounds that fully address these concerns.

    We would like to formally submit the following feature requests for consideration, as these enhancements could significantly improve user productivity and overall user experience.

    1. Persistent Alphabetical Folder Sorting Preference

    Current Behavior: Users frequently need to manually reapply alphabetical sorting when navigating through folders. The system often reverts to previously used sorting methods, requiring additional clicks and page refreshes.

    Requested Enhancement: Provide a user-level or enterprise-level setting that allows users or administrators to define a default folder sorting preference, such as:

    Sort by Name (A-Z)
    Sort by Name (Z-A)
    Sort by Date Modified
    Sort by Size

    The selected preference should persist across:

    All Box web sessions
    Folder navigation
    Browser refreshes
    Future logins

    Business Impact: For users working in large and deeply nested folder structures, repeatedly applying sorting preferences creates unnecessary clicks, increases load times, and reduces efficiency during routine file searches.

    1. Intelligent "Save As" Folder Recognition

    Current Behavior: When performing a "Save As" operation on an existing document, users are often taken back to a higher-level parent folder or the last-used location rather than the folder where the current document is stored.

    Requested Enhancement: When a user opens an existing file from Box and selects Save As, Box should automatically suggest or navigate to the file's current folder location as the default save destination.

    Expected Experience: This would mirror the behavior users experience with other cloud storage platforms, where the most logical save destination is the folder containing the source document.

    Business Impact: Users working within complex folder hierarchies currently need to manually navigate through multiple folder levels each time they perform a Save As operation. This results in:

    Additional clicks
    Increased time spent locating folders
    Greater risk of saving files in incorrect locations
    Reduced overall productivity
    Summary

    These are not defects but usability enhancements that would provide meaningful efficiency gains for users who work extensively within structured folder environments. We believe both capabilities would improve the overall Box experience and reduce friction during common document management tasks.

    We kindly request that these ideas be reviewed by the Product Management team and considered for inclusion in the Box product roadmap.

    Thank you for your consideration.

    Please reach us at "james.baldwin@ogilvy.com & harish.andyala@kyndryl.com" for more information.

    Thanks & Regards,
    Harish A
    harish.andyala@kyndryl.com

    Hello Box Product Team,

    I recently provided feedback and requested an feature enhancement in the box support case "#3631047".

    Thank you for reviewing our feedback. We understand that the current behavior is working as designed and that there are currently no administrative settings or workarounds that fully address these concerns.

    We would like to formally submit the following feature requests for consideration, as these enhancements could significantly improve user productivity and overall user experience.

    1. Persistent Alphabetical Folder Sorting Preference

    Current Behavior: Users frequently need to manually reapply alphabetical sorting when navigating through folders. The system often reverts to previously used… 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  ·  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

14. Request Box Drive be supported on Windows 2012 R2
    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  ·  Desktop  ·  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. Include .NET 4.5.2 in Box Drive install package
    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  ·  Desktop  ·  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. 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

17. Develop v2 Integration for Scalable Deployment of Box Within Connections
    0 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

    not planned  ·  0 comments  ·  Partner Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Add all webhooks v2 event triggers to the Java SDK

    It's currently unclear whether all event triggers listed in developer docs are supported, as the Java SDK does not specifically list them: https://github.com/box/box-java-sdk/blob/master/src/main/java/com/box/sdk/BoxWebHook.java#L584

    0 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  ·  Developer Platform  ·  Delete…  ·  Admin →
    delivered  ·  AdminDan Dennhardt (Product Manager, Box) responded

    This has been addressed in https://github.com/box/box-java-sdk/pull/497

19. Integration with Pardot

    B2B Marketing Software, from Salesforce

    0 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

    not planned  ·  0 comments  ·  Partner Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Create API request for retentions with a file or ID as a param. Create an API call for a folder with retention policies applied.

    (https://api.box.com/2.0/file_version_retentions)

    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

    not planned  ·  0 comments  ·  Governance  ·  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