408 results found

1. Box for Netsuite - lock permissions for an accounting period
   2 votes

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

2. The option to invite users as Editor when Box for Teams creates a Chat Folder

   Box for Teams currently invites users as co-owner in Chat folder which is too strong permission. Admin don't allow end-users to have any inviting permission in any other folders but it creates a backdoor when Box for Teams is enabled

   7 votes

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

3. Ability to disable channel folder changes by users (including team owners)

   Currently, users can change the location of their "Microsoft Teams Chat Files" folder and team owners can change the location of channels' folders.
   Due to security concerns, customers want to have the ability to disable folder changes for channels and chats.

   2 votes

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

4. Limit the federated search results to files under salesforce root folder

   Limit the federated search results to files under salesforce root folder.

   4 votes

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

5. Airtable

   Security, sustainability, traceability and file management headaches would be significantly reduced if a file existed in one place, under a single corporate entity, with a single set of permissions and shared across integrations.

   It would be awesome if a file in Box could be published into an Airtable attachment field in an airtable record without copying it into the Airtable tenant and consuming storage.

   If a Box link were dragged into an Airtable attachment field and dropped, could Airtable interrogate the file permissions in Box to see if it is allowed? If so, present the thumbnail provided by Box as a preview. Click on the link, and it provides the Box preview as it does today and download capability. If the user's Box login could authenticate download, that would be amazing.

   Allowing the API to establish the link would be essential.

   Sustainability +++ Security +++ Ease of use +++

   Security, sustainability, traceability and file management headaches would be significantly reduced if a file existed in one place, under a single corporate entity, with a single set of permissions and shared across integrations.

   It would be awesome if a file in Box could be published into an Airtable attachment field in an airtable record without copying it into the Airtable tenant and consuming storage.

   If a Box link were dragged into an Airtable attachment field and dropped, could Airtable interrogate the file permissions in Box to see if it is allowed? If so, present the thumbnail provided by Box as… more

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

6. Allow Co-Authoring to dynamically check document sync status

   Currently, if an Office document is opened before being synced to Box, the Co-Authoring features are unavailable. The document must be closed and re-opened to refresh the sync status.
   It would be good if the document could check it's sync status periodically while open and adapt on the fly.

   Seamless integration as Microsoft Teams collaboration

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

7. Box for Teams Content Card Support for Group Invites

   We have confirmed that when collaborating as a group rather than as a direct collaborator, the content card behaves differently than described in the article.
   After investigating with your company (Box), we were told that content card behavior for group invitations is not currently supported.
   Therefore, to avoid confusion for users, we would like you to take the following action.

   　【Requests】：
   　　1.The article should clearly state that the operation of content cards for group invitations is not currently supported.
   　　2.In the future, we would like to see content cards for group invitations also be supported.

   　【Target article】：
   　　Using Box for Teams：https://support.box.com/hc/en-us/articles/360044681474

   　【Checked behavior】：
   　　1.Content card not updating even after granting access permissions

   　　　Article Contents：
   　　　　To Post a shared link from Box in a Teams Channel or Chat:
   　　　　5.Once you grant the access, the card refreshes to show the content card with file details.

   　　　Actual behavior：
   　　　　When attempting to grant access, the message "Response sent to app" is displayed, but the card is not updated and the card for granting permissions remains displayed.
   　　　　*It has been confirmed that the posted Box shared link itself can be sent to the other party and that the other party has received it.。

   　　2.Even if the same operation is performed, the number of inaccessible chat members displayed on the content card may differ.

   　　　Article Contents：
   　　　　Difference between Channels and Chats
   　　　　・When sharing a file in a chat message, Box indicates the specific number of chat members who lack access (it does not indicate this in a channel message).
   　　　　 By granting members access to the file, you are making them collaborators (as compared to channel members, to whom you’re simply granting file access).
   　　
   　　　Premise：
   　　　　・The sender, recipient A, and recipient B belong to the same group.
   　　　　・All three were invited to the shared link folder as part of a group, and were not direct collaborators.
   　　　　・The group has editor privileges

   　　　Actual behavior：
   　　　　・When the sender sends a chat to recipient A: The content card displays the message "You cannot view this file shared by two users."
   　　　　・When the sender sends a chat to recipient B: The content card displays the message "You can't view this file shared by a user."

   ＜Box for Teamsのグループ招待時のコンテンツカードのサポートについて＞
   直接的なコラボレータではなく、グループとしてコラボレートされている場合、コンテンツカードで記事と異なる動作を確認しております。
   貴社（Box社）に調査いただいたところ、グループ招待のコンテンツカードの動作は、現状サポートされていない旨回答いただきました。
   そこでユーザーの混乱を招かないよう、以下ご対応いただきたく存じます。

   　【依頼事項】：
   　　1.グループ招待のコンテンツカードの動作は、現状サポートされていないことを記事に明記
   　　2.将来的にグループ招待のコンテンツカードもサポート対象とする

   　【対象記事】：
   　　Box for Teamsの使用：https://support.box.com/hc/ja/articles/360044681474

   　【確認している動作】：
   　　1.アクセス権限を付与してもコンテンツカードが更新されない

   　　　記事の内容：
   　　　　TeamsチャネルまたはチャットでBoxから共有リンクを投稿するには:
   　　　　5.アクセス権限を付与すると、カードは更新され、ファイルの詳細を含むコンテンツカードが表示されます。

   　　　実際の動作：
   　　　　アクセス権限を付与しようとすると「応答がアプリに送信されました」と表示されるものの、
   　　　　カードは更新されず、権限付与するためのカードが表示され続けたままの状態となる。
   　　　　※投稿したBoxの共有リンク自体は、相手方に送信でき、相手方も受信できていることを確認済み。

   　　2.同じ操作にもかかわらず、コンテンツカードに表示されるアクセスできないチャットメンバー数に差異が生じる場合がある

   　　　記事の内容：
   　　　　チャネルとチャットの相違点
   　　　　・チャットメッセージでファイルを共有すると、アクセスできないチャットメンバーの具体的な数が表示されます (これは、チャネルメッセージでは表示されません)。
   　　　 　ファイルへのアクセスをメンバーに許可すると、そのメンバーはコラボレータになります (チャネルメンバーの場合は、ファイルへのアクセスを許可するだけです)。
   　　
   　　　前提：
   　　　　・送信者、送信先A、送信先Bは、同一グループに所属している
   　　　　・3名とも共有リンクのフォルダにはグループとして招待されており、直接的なコラボレータではない
   　　　　・グループとして編集者権限はある

   　　　実際の動作：
   　　　　・送信者⇒送信先Aにチャットを送信した場合：コンテンツカードに「2人のユーザーが共有したこのファイルを表示できません」と表示される。
   　　　　・送信者⇒送信先Bにチャットを送信した場合：コンテンツカードに「1人のユーザーが共有したこのファイルを表示できません」と表示される。

   We have confirmed that when collaborating as a group rather than as a direct collaborator, the content card behaves differently than described in the article.
   After investigating with your company (Box), we were told that content card behavior for group invitations is not currently supported.
   Therefore, to avoid confusion for users, we would like you to take the following action.

   　【Requests】：
   　　1.The article should clearly state that the operation of content cards for group invitations is not currently supported.
   　　2.In the future, we would like to see content cards for group invitations also be supported.

   　【Target article】：
   　　Using Box for… more

   3 votes

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

8. Request for improvement of behavior when posting a shared link of a Box folder in a Teams channel or chat

   When you post a Box shared link in a Teams channel or chat, you'll see a Grant Access card with the option to grant users additional permissions if the following conditions are true:

   　condition：If there are channel members or chat members who do not have access permissions to the shared folder or file.
   　　　　　　＊This includes channel members and chat members who are invited as a group but not directly invited as users.

   The support article states that when you grant access, the card will update and a content card with file details will be displayed.
   However, when you post a shared link for a folder and grant access, although it says "A response has been sent to the app,"
   the card does not update and the card for granting permissions continues to be displayed.

   After investigating, we received a response from your company (Box) stating that the content of the support article only applies to files and that this is currently the expected behavior.
   However, in addition to files, shared links to folders are sometimes posted, and the current behavior is confusing to users.
   For this reason, we would like to see this improved so that the behavior for folders is the same as for files.

   　　＊Using Box for Teams：https://support.box.com/hc/en-us/articles/360044681474
   　　　「Posting a link from Box in a Teams Channel or Chat」
   　　　5.Once you grant the access, the card refreshes to show the content card with file details.

   ＜TeamsチャネルまたはチャットでBoxのフォルダの共有リンクを投稿した場合の動作改善依頼＞
   以下に該当する場合、TeamsチャネルまたはチャットでBoxの共有リンクを投稿すると、ユーザーに追加の権限を付与するためのオプションを含む、アクセス権限を付与するためのカードが表示されます。

   　条件：共有するフォルダまたはファイルへの、アクセス権限を持っていないチャネルメンバーやチャットメンバーがいる
   　　　　※グループとして招待されているものの、ユーザーとして直接招待されていないチャネルメンバーやチャットメンバーも含む
   　　　
   サポート記事では、アクセス権限を付与すると、カードは更新され、ファイルの詳細を含むコンテンツカードが表示される旨記載されています。
   しかし、フォルダの共有リンクを投稿し、アクセス権限を付与する操作を実施すると、「応答がアプリに送信されました」と表示されるものの、
   カードは更新されず、権限付与するためのカードが表示され続けたままの状態になります。

   調査の結果、貴社（Box社）より本動作について、サポート記事の内容はファイルのみが対象であり、現在の想定動作である旨返答いただいております。
   しかし、ファイルだけでなく、フォルダの共有リンクも投稿することがあり、現在の動作はユーザーの混乱を招いてしまいます。
   そのため、フォルダの場合もファイルと同じ動作となるよう、改善を希望いたします。

   　　＊Box for Teamsの使用：https://support.box.com/hc/ja/articles/360044681474
   　　　「TeamsチャネルまたはチャットでBoxのリンクを投稿する」
   　　　5.アクセス権限を付与すると、カードは更新され、ファイルの詳細を含むコンテンツカードが表示されます。

   When you post a Box shared link in a Teams channel or chat, you'll see a Grant Access card with the option to grant users additional permissions if the following conditions are true:

   　condition：If there are channel members or chat members who do not have access permissions to the shared folder or file.
   　　　　　　＊This includes channel members and chat members who are invited as a group but not directly invited as users.

   The support article states that when you grant access, the card will update and a content card with file details will be displayed.
   However, when you post a… more

   3 votes

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

9. Expand a limitation of search result over 50 for Federated Search in Salesforce integration.

   Expand a limitation of search result over 50 for Federated Search in Salesforce integration.

   3 votes

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

10. Please be able to specify which users can use the Box Graph Connector.

    Currently, the Box Graph Connector is enabled for users tenant-wide, but we would like to be able to enable it for specific users.

    For example, if some users are using Copilot for Microsoft 365, we need to be able to specify that only users who can use Copilot for M365 can use Box Graph Connector.

    6 votes

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

11. Provide Box plugin for Microsoft 365 Copilot

    Copilot plug-ins have the advantage that data can be handled in real time, and there are no limit to the number of items, etc.

    In addition to the Graph Connector, the Box plug-in for Copilot integration is also required.

    Appendix.

    https://learn.microsoft.com/ja-jp/microsoft-365-copilot/extensibility/

    5 votes

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

12. Copilot support in Office Online/Office desktop applications for files on Box

    Currently, Copilot (Copilot in Word/Excel/PowerPoint) is not supported for Office files in Box.

    The following must be supported for files in Box

    (1) Copilot in Office Online

    (2) Copilot in Office desktop applications (with or without co-authoring)

    Appendix.

    https://support.microsoft.com/en-us/office/i-am-getting-license-validation-errors-with-copilot-375cf342-8559-48c3-8436-7564d5de3fc6#:~:text=Check%20that%20your%20file%20is%20in%20the%20right%20location%C2%A0

    4 votes

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

13. Request for improvement of the UI for granting permissions displayed on the content card in Box for Teams

    If you try to grant permission before sending a message, you will see the error message "Return to the main window to perform this action"
    We are aware that this behavior is documented in a support article.
    However, the permission prompts on the content cards are confusing because they seem to require immediate action to grant permissions.
    We would like to see the UI improved so that it is clear that permissions can only be granted after the message has been sent.

    　suggestion1：Display a message that lets users know that they cannot grant permission until after they send a message.
    　suggestion2：Display permission grant message in permission prompt on content card after sending message

    ＊Using Box for Teams：https://support.box.com/hc/en-us/articles/360044681474

    　「To Post a shared link from Box in a Teams Channel or Chat:」
    　4.You need to send the message before you can grant permissions. If you try to grant permissions before sending the message, an error message Return to the main window to perform this action appears.

    ＜Box for Teamsの、コンテンツカードに表示される権限付与のUI改善依頼＞

    メッセージ送信前に、権限を付与しようとすると、「メインウィンドウに戻って、この操作を実行してください。」というエラーメッセージが表示されます。
    この動作について、サポート記事に記載されていることは承知しております。
    しかし、コンテンツカードの権限のプロンプトでは、その場で権限付与の対応を求めているような表示であり、混乱します。
    メッセージの送信後でないと、権限付与ができないことが分かるように、UIの修正を希望します。

    　案1：メッセージ送信後でないと、権限付与ができないことが分かるようなメッセージを表示にする
    　案2：メッセージ送信後に、コンテンツカードの権限のプロンプトで権限付与のメッセージを表示する

    ＊Box for Teamsの使用：https://support.box.com/hc/ja/articles/360044681474

    　「TeamsチャネルまたはチャットでBoxの共有リンクを投稿する」
    　4.権限を付与する前に、メッセージを送信する必要があります。 メッセージの送信前に権限を付与しようとすると、メインウィンドウに戻って、この操作を実行してください。 というエラーメッセージが表示されます。

    If you try to grant permission before sending a message, you will see the error message "Return to the main window to perform this action"
    We are aware that this behavior is documented in a support article.
    However, the permission prompts on the content cards are confusing because they seem to require immediate action to grant permissions.
    We would like to see the UI improved so that it is clear that permissions can only be granted after the message has been sent.

    　suggestion1：Display a message that lets users know that they cannot grant permission until after they send a message.… more

    12 votes

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

14. Request for improvement to the number of users without access displayed on the content card in Box for Teams

    If the user has only been invited as a group, they will be counted and shown as "without access" even though they have access permissions because they are not a direct collaborator.
    We are aware that this behavior is documented in a support article.
    However, the display differs from the actual situation and may induce incorrect responses, as described below.
    Therefore, we would like to request a fix so that it shows the accurate number of users without access, whether they are direct collaborators or group collaborators.

    　ex）
    　1.Even though the target user has access rights as a group, there is a risk that the user may be deemed to not have access rights and may be given access rights again as an individual user.
    　2.Even if access rights are truly required, there is a risk that the current incorrect display of the number of users without access rights will lead to missed access rights being granted.

    ＊Using Box for Teams：https://support.box.com/hc/en-us/articles/360044681474

    　「Difference between Channels and Chats」
    　・In addition, the permissions prompt displays if other users in the chat already have access to the file through a user group, but are not direct collaborators on the file.

    ＜Box for Teamsの、コンテンツカードに表示される、アクセス権のないユーザー数の改善依頼＞

    グループとしてのみ招待されている場合、アクセス権限があるにもかかわらず、直接的なコラボレータではないため、「アクセス権がない」ユーザーとしてカウントされ、表示されます。
    この動作について、サポート記事に記載されていることは承知しております。
    しかし、実際の状況とは異なる表示となっており、以下のように誤った対応を誘発する可能性があります。
    そのため、直接的なコラボレータ、グループのコラボレータにかかわらず、アクセス権のないユーザーの正確な数を表示するよう、修正を希望します。

    　例）
    　1.グループとしてアクセス権があるのに、アクセス権がないものと判断し、ユーザーとして個別に再度アクセス権を付与してしまう。
    　2.本当にアクセス権の付与が必要な状態にもかかわらず、現状の誤った、アクセス権のないユーザー数の表示の影響、と誤認し、アクセス権付与の対応が漏れが発生してしまう。

    ＊Box for Teamsの使用：https://support.box.com/hc/ja/articles/360044681474

    　「チャネルとチャットの相違点」
    　・さらに、チャットの他のメンバーがすでにユーザーグループ経由でファイルへのアクセス権限を持っているものの、ファイルの直接的なコラボレータではない場合に、権限のプロンプトが表示されます。

    If the user has only been invited as a group, they will be counted and shown as "without access" even though they have access permissions because they are not a direct collaborator.
    We are aware that this behavior is documented in a support article.
    However, the display differs from the actual situation and may induce incorrect responses, as described below.
    Therefore, we would like to request a fix so that it shows the accurate number of users without access, whether they are direct collaborators or group collaborators.

    　ex）
    　1.Even though the target user has access rights as a group, there… more

    12 votes

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

15. Integrate Box for Microsoft Teams with multiple Microsoft tenants

    The Box for Microsoft Teams integration currently requires a 1 to 1 mapping with a Microsoft tenant. We would like the ability to enable this integration across multiple tenants while maintaining a single Box EID.

    4 votes

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

16. Google Sheet from Box doesn't have the 'Protect Sheet' feature

    Hi,

    I have created a Google Sheet from Box but I can't 'Protect Sheet' to prevent collaborators from doing any editing. I only want them to open and view the contents via Google Sheet.

    The 'Protect Sheet' feature is not available when I open the Google Sheet from Box. Please assist on this.

    Thanks,

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

17. Auto "Add Box to this Chat" in Teams

    With Box for MS Teams, you can use an App Setup Policy in Teams so the Box app always shows under your chat box so you can easily find it. With that, if you select it and choose one of the options for Upload or Share, you are then prompted to "Add Box to this Chat".

    Can that just be automatically added to all chats and channels?

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

18. Support for Context Menu Actions on Multiple Files in Box Integrations

    developer community post

    Dear Box Product Team,

    I hope this message finds you well. I recently reached out regarding an issue I encountered while developing an integration for Box, specifically related to context menu actions on multiple files. Upon discussing the matter with your developer advocate, I was informed that the behavior I observed, where context menu options are not available for multiple file selections, is by design.

    While I understand that there may be considerations and design decisions behind this behavior, I would like to provide feedback from a developer's perspective. It would greatly enhance the flexibility and usability of Box integrations if there were an option for developers to declare whether their integration supports actions on multiple files. Additionally, providing support for receiving a list of file IDs or triggering multiple requests could streamline workflows and improve the overall user experience.

    As a developer working with Box's platform, I believe that offering such functionality would open up new possibilities for creating more efficient and powerful integrations. This feedback is based on my own experience and the needs of developers who rely on Box's platform to build custom solutions for their organizations and clients.

    I appreciate the opportunity to share this feedback with you, and I trust that it will be considered as you continue to evolve and improve the Box platform. Thank you for your attention to this matter, and I look forward to seeing how Box integrates user feedback into future updates and enhancements.

    Best regards,
    Sarin

    developer community post

    Dear Box Product Team,

    I hope this message finds you well. I recently reached out regarding an issue I encountered while developing an integration for Box, specifically related to context menu actions on multiple files. Upon discussing the matter with your developer advocate, I was informed that the behavior I observed, where context menu options are not available for multiple file selections, is by design.

    While I understand that there may be considerations and design decisions behind this behavior, I would like to provide feedback from a developer's perspective. It would greatly enhance the flexibility and usability… more

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

19. Allow the selection of multiple files at once to send to Box in the Google Workspace Box Add On

    It's currently not possible to select multiple files to add to box when using the Google Workspace Add On. This would be useful.

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

20. Salesforce Flow Action to Upload by ContentDocument.ID

    Provide a new Flow Action to support uploading EmailToCase Files and other ContentDocuments to Box. Ideally this would support Files larger than 10-12mb in size.

    1 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  ·  Partner Integrations  ·  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