411 results found

1. We would like the usage standards for Box Connector for Microsoft Graph to be relaxed.

   Currently, the Box Connector for Microsoft Graph requires fewer than 10,000 Box users, but the improved interoperability between Box and Microsoft products is more beneficial for larger tenants.
   I would like the user limit to be increased or eliminated.

   Additionally, We can currently search and display Box content (up to 20,000 recent items) across the Microsoft ecosystem, but this amount of content is not very searchable, so we'd like to see as many as possible.

   https://support.box.com/hc/en-us/articles/4403605037587-Box-Graph-Connector

   Box Connector for Microsoft Graphの利用基準を緩和してほしい

   現在、Box Connector for Microsoft Graphを利用するにはBoxユーザーが10,000人未満であることが条件ですが、Box製品とMicrosoft製品間の相互運用性の向上は、大人数のテナントでより効果的です。
   ユーザー数の上限を引き上げるか、なくしてほしいです。

   また現在は、Microsoftのエコシステム全体でBoxのコンテンツ (最大20,000の最新項目) を検索して表示できますが、このコンテンツ数では検索性が低いため、可能な限り多くしてほしいです。

   https://support.box.com/hc/ja/articles/4403605037587-Box-Graph-Connector

   56 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

   under consideration  ·  1 comment  ·  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. 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

   21 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. 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

   8 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. 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

5. 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

6. 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.

   9 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

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

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

9. 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/

   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

10. Edit files shared on Microsoft Teams chats without having to preview them first

    Currently, when a file is shared on a Microsoft Teams chat, there is a sharing card with two buttons: Preview and Edit.
    When the recipient of the shared link clicks on Edit first, an error is shown saying "Office Online failed to load", which apparently is caused by the lack of edit permissions to the file. In other words, clicking the Edit button doesn't add the necessary permissions.
    On the other hand, clicking on the Preview button works fine and file is displayed as expected. After previewing, clicking on Edit also works because apparently the recipient of the shared link is added as a collaborator when previewing the file.
    Currently there's no indication that users should click on the Preview button first or add the recipients as collaborators directly on Box, so it's confusing for users.
    Ideally, the Edit button would also add the necessary permissions before opening the Edit screen.

    Currently, when a file is shared on a Microsoft Teams chat, there is a sharing card with two buttons: Preview and Edit.
    When the recipient of the shared link clicks on Edit first, an error is shown saying "Office Online failed to load", which apparently is caused by the lack of edit permissions to the file. In other words, clicking the Edit button doesn't add the necessary permissions.
    On the other hand, clicking on the Preview button works fine and file is displayed as expected. After previewing, clicking on Edit also works because apparently the recipient of the shared link… 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

11. Google and Microsoft FORMS integration is missing!

    I see that this is not planned based on lack of demand. I'm writing this comment to increase the demand.

    I will continue to use SharePoint or Google drive because this is missing from box.

    Word, PPT, Excel, Google docs, slides and sheets are all here... why not forms?

    •  

    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

12. Simplify access to box sign and match other vendors' capability

    Add box sign as an option in Microsoft Teams "Approvals" (just like Adobe, Docusign and Sharepoint have ;-) )

    •  

    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

13. 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

14. 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

15. 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

16. 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

17. 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

18. The ability to have an option to disable the auto folder creation of "Microsoft Teams Chat Files"

    We would like to have an option to configure the folder creation of Box for Teams. For organizations that don't allow users to use Box as personal folder, Microsoft Teams Chat Files should be off and is controllable based on the needs.

    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

19. Enhanced Permissions for Locked Accounting Periods in Box for Netsuite Integration

    It would be helpful for the integration to change all permissions to Viewer for transactions in a locked accounting period. This would ensure data retention. I realize we could use "Viewer Uploader", however, accountants need delete permissions (i.e. "Editor") until the accounting period is closed.

    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. Save Microsoft Teams Recordings to Box

    When recording a call/meeting in Microsoft Teams, it defaults to using OneDrive as it's default storage. Currently the process of saving a recording is a manual process of downloading the recording, and uploading to Box. I'd like an option to default recording data to Box instead.

    16 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

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