669 results found

1. Security Report: Log when apps are disabled/enabled in the Admin Console

   Currently, when admins/co-admins mark apps as 'available' or 'disabled' in the Admin Console -> Enterprise Settings -> Apps page, no reporting event is triggered, meaning companies have no way to self-identify who enabled/disabled which applications/endpoints, and this is a major security concern for some customers.

   REQUEST: Add entries to the Security Report in the admin console whenever:
   1. A published app's status is changed between Available, Disabled, and Added by Default (via the Enterprise Settings -> Apps page)
   2. An API key is added/removed from the Unpublished Applications Whitelist field on Enterprise Settings -> Apps

   14 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  ·  Partner Integrations  ·  Delete…  ·  Admin →
   delivered  ·  AdminMarek Podgórski (Admin, Box) responded

   We are happy to announce that we have addressed this request. Details are available in the announcement.

   Box Partner Integrations Team

2. Enhance the Box for DocuSign Integration in terms of metadata

   We would like to put some information of DocuSign Envelope (such as contract data, term of contract, type of contract etc.) into Box metadata instance in an automated way. Currently, there's two ways users would be able to do are; 1. users manually populate metadata such as transaction amount in signed document or 2. using iPaaS (Workato) to automate populating metadata. No.1 is inefficient and time-consuming and has human-error risk. No.2 requires additional cost. This is actually required by Japanese local law when we save financial documents digitally. The law is called Denshi Chobo Hozon Hou. This becomes a huge roadblock for box/DocuSign customers to implement/adopt both systems for use-cases associated with saving signed financial documents in Box.

   For the law of Denshi Chobo Hozon hou (https://www.nta.go.jp/law/joho-zeikaishaku/sonota/jirei/05.htm), please find the google-translated excerpt below

   ---

   Requirement 5
   Ensuring search function Article 3, Paragraph 1, Item 5 of the Enforcement Regulations
   Secure a search function that meets the following requirements for electromagnetic records related to books
   (B) The main record items according to the transaction date, account, transaction amount, and other types of books can be set as search conditions.
   (B) For record items related to dates or amounts, conditions can be set by specifying the range.
   (C) Conditions can be set by combining two or more arbitrary recording items.

   ---

   We would like to put some information of DocuSign Envelope (such as contract data, term of contract, type of contract etc.) into Box metadata instance in an automated way. Currently, there's two ways users would be able to do are; 1. users manually populate metadata such as transaction amount in signed document or 2. using iPaaS (Workato) to automate populating metadata. No.1 is inefficient and time-consuming and has human-error risk. No.2 requires additional cost. This is actually required by Japanese local law when we save financial documents digitally. The law is called Denshi Chobo Hozon Hou. This becomes a huge… more

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

3. Fix custom logo resolution & display issues

   Presently there are two main issues that Box needs to fix with the way it displays custom company logos:

   1. Custom logos display at an extremely low resolution. It's 2023 and our company's logo looks blurry and very bad on most screens. Logos used in the Box Sign branding are crisp and high resolution and look great. This is not the case for logos used within the standard Box file management platform though. Please fix this.

   2. Right now Box has the option to upload 2 different versions of your company logo. One for use on a white background and one for use on your 'brand color' background. This is great, but due to a bug I have been reporting for years, Box in certain cases will display the wrong logo version. For example, on a shared public link to a file (not a folder), it has a white banner at the top of the screen and it displays the "logo for use on brand color" instead of the correct "logo for use on white." This is just a bug that needs to be fixed.

   In short, please fix the way that custom company logos display in Box. Our clients are interacting with our files and it is important that our brand is represented in a way that looks professional and displays our logo correctly.

   Presently there are two main issues that Box needs to fix with the way it displays custom company logos:

   1. Custom logos display at an extremely low resolution. It's 2023 and our company's logo looks blurry and very bad on most screens. Logos used in the Box Sign branding are crisp and high resolution and look great. This is not the case for logos used within the standard Box file management platform though. Please fix this.

   2. Right now Box has the option to upload 2 different versions of your company logo. One for use on a white background and one for… more

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

4. Add faster playback speed for audio files (1.1-2x)

   Pretty self explanatory, would allow for optimal audiobook/podcast/Mp3 playback

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

5. Fix Version History for Co-Authored Files

   Now that co-authoring is available on Office files (which is a great feature!) version history is paying the price. On files that are edited often, the version history is growing out of control which leads to two primary issues:

   1 - Since only the last 100 versions of a file are available, the significant increase in versions caused by co-authoring means you may only have a few days worth of version history instead of months or years of history. Consider more version history and/or the ability to specify on a file how often an "accessible" version is saved for viewing later (say once a day or once a week for instance).

   2 - The version history pane is very slow to load. Some performance optimizations are needed for the large increase in versions.

   Now that co-authoring is available on Office files (which is a great feature!) version history is paying the price. On files that are edited often, the version history is growing out of control which leads to two primary issues:

   1 - Since only the last 100 versions of a file are available, the significant increase in versions caused by co-authoring means you may only have a few days worth of version history instead of months or years of history. Consider more version history and/or the ability to specify on a file how often an "accessible" version is saved for viewing… more

   10 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

   2 comments  ·  Box for Office  ·  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. Fix accessibility of iOS app please

   Please make the iOS app more accessible.

   Issue: When navigating folders, focus is on the wrong folder and there is no way to fix it. To replicate, turn on VoiceOver and drag your finger over the folders to navigate and hear them read aloud, stopping before you get to the bottom of the page. Then swipe to navigate through the folders. By the time you get to the bottom of the first page's list, the focus is lost and the only way to get it back is to kill the app and restart it. Frustrating when you have multiple pages of folders and you can't get past the first page.

   This does not occur on Android.

   Broken as of Feb 2019.

   Demo of issue: https://ucdavis.box.com/s/an8zmd8dptaqf0ujglu1yvsc2cug1g8j

   Please make the iOS app more accessible.

   Issue: When navigating folders, focus is on the wrong folder and there is no way to fix it. To replicate, turn on VoiceOver and drag your finger over the folders to navigate and hear them read aloud, stopping before you get to the bottom of the page. Then swipe to navigate through the folders. By the time you get to the bottom of the first page's list, the focus is lost and the only way to get it back is to kill the app and restart it. Frustrating when you have multiple pages… more

   6 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  ·  Mobile  ·  Delete…  ·  Admin →

7. I would like to see 4 hours added to the session duration section.

   I would like to see 4 hours added to the session duration section.

   【Current Specifications】
   In the current pull-down menu for session duration, there are only 8 hours after 2 hours.

   【background】
   We feel that the current 2 hours is too short and 8 hours is too long.
   We would like to increase the number of items for session duration to better meet the needs of users.

   (日本語)
   セッション持続時間の項目に4時間を追加して欲しい

   【現在の仕様】
   セッション持続期間が現在のプルダウンメニューでは、2時間の次は8時間しかありません。

   【背景】
   利用する中で現在の2時間では短く、8時間では長いと感じています。
   セッション持続期間の項目を増やすことで、利用者ニーズに細かく対応したいため。

   6 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

   2 comments  ·  Admin Console  ·  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. Folder-level "custom terms of service"

   Is it possible to only setup "Custom Terms of service" on specific sub-folders for external collaborators? Or is this setting only account-wide??

   Use case:

   We have a dataroom set up, and some external collaborators have problems accessing the "login custom terms of service" NDA and logging into Box. The notification emails from the system are often sent to their spam folder.

   We can send an NDA via the "e-sign" feature, but don't want our external collaborators to then have to accept it a 2nd time when they come to a (separate, for NDA e-signers) dataroom folders.

   Can we setup a folder-level NDA/Custom terms of service? then we can have 2 versions of the dataroom.

   1 has the click-through NDA/custom terms of service

   2 is for people who e-sign the NDA, and then can enter without having to do a "clickthrough custom terms of service/NDA" a 2nd time

   Is it possible to only setup "Custom Terms of service" on specific sub-folders for external collaborators? Or is this setting only account-wide??

   Use case:

   We have a dataroom set up, and some external collaborators have problems accessing the "login custom terms of service" NDA and logging into Box. The notification emails from the system are often sent to their spam folder.

   We can send an NDA via the "e-sign" feature, but don't want our external collaborators to then have to accept it a 2nd time when they come to a (separate, for NDA e-signers) dataroom folders.

   Can we setup a… more

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

9. ability to format number field in metadata display to show fixed number of decimal places and commas

   Number fields uploaded as float with 2 decimal places do not display decimals if the digit is 0. Is there a way to format numbers to display as currency format #,###.##? Please add this feature especially useful for using in Box Apps.

   5 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  ·  Box Apps  ·  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

10. Automated File renaming (at scale) - Programmatic creation of workflows

    When a file is moved to any folder called “#Archive”, the file should be renamed with a prefix of “OLD_”

    For example: I have a file called “mywordfile.docx” I now want to archive this file, so I drag it into a folder call “#Archive”. Box Automation should then rename my file to “OLD_mywordfille.docx”

    Problem statement
    The box automation trigger “when file moved to folder” requires an explicit folder path. Meaning I would need to configure a rule per “#Archive” folder within our folder structure. We have many. So, manually setting up relay for every single #Archive folder is not a scalable solution.

    Possible Solution 1.
    Feature request for Relay triggers to support wild cards. Eg: When file moved to */#Archive, a trigger action = true

    Possible Solution 2.
    Programmatic deployment of the current workflow. Eg: Parse through are folder structure, when finding a folder called #Archive, then apply workflow to rename file. This would require the ability to programmatically deploy workflows via the API.

    When a file is moved to any folder called “#Archive”, the file should be renamed with a prefix of “OLD_”

    For example: I have a file called “mywordfile.docx” I now want to archive this file, so I drag it into a folder call “#Archive”. Box Automation should then rename my file to “OLD_mywordfille.docx”

    Problem statement
    The box automation trigger “when file moved to folder” requires an explicit folder path. Meaning I would need to configure a rule per “#Archive” folder within our folder structure. We have many. So, manually setting up relay for every single #Archive folder is not a… more

    6 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  ·  Workflow  ·  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. Right now, Box's search engine is kinda useless

    So, i contacted Box through chat to ask why the search engine wasn't looking for the specific input i searched for, and among other things i was told that the engine will look for files/folders which match ANY of the words in your input and has no capability of looking for files containing ALL of the words searched for which most search engine have, be it web search or OS search.

    So, here's the problem, we have around 10.000 files uploaded to box, and lots of them share several words which indicate the client's name or what the file contains. So if i have a file called, for example "GAT Flyer Expo 2020", and look for "gat flyer expo 2020", instead of looking for a file with ALL of those words in it's name, it will look for any files that contain any of those words, resulting in 2.000+ results, of which i then have to manually search for file i was looking for, which defeats the purpose of a search engine.

    So, Box's engine should have the capability to search for files that contain all of the words in the input, instead of looking for files containing any of the words. Kinda imperative as a function i'd say.

    So, i contacted Box through chat to ask why the search engine wasn't looking for the specific input i searched for, and among other things i was told that the engine will look for files/folders which match ANY of the words in your input and has no capability of looking for files containing ALL of the words searched for which most search engine have, be it web search or OS search.

    So, here's the problem, we have around 10.000 files uploaded to box, and lots of them share several words which indicate the client's name or what the file contains.… more

    6 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  ·  Search  ·  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. Select multiple folders as the location filter for Views in Box Apps

    I would like the ability to select multiple folders as the location filter for Views in Box Apps. For example, I may have a project folder with a metadata template cascading to all subfolders, but I only want to see content from 2 out of the 3 subfolders in the View.

    6 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  ·  Box Apps  ·  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. Cleanup and Enhance the file/folder webhook events to cover all the happy paths (new file, new file version, restore previous version)

    As a Box Application Developer I want to be able to receive a unique, webhook events for the following scenarios:

    1. User uploads new file (brand new binary object placed into a Box Folder) - Folder based event (exists: FILE.UPLOADED)
    2. User uploads a new file version - File AND Folder based event (e.g. FILE_NEW.VERSION)
    3. User restores a previous file version - File AND Folder based event (e.g. FILE_RESTORE.VERSION)

    As the owner of an enterprise application that has deep integration in the BOX platform, it is surprising that I have no way to use the Webhooks to monitor files for new versions and restoring of previous version while only having new file versions tied to the folder.

    The existing event of File.Upload is not connected to the file event, which is an issue. In addition it covers more than one event, a new file in the folder and a new file version to a file in that folder.

    t is not a good practice to have different application actions covered by the same event as it adds complexity to application developers when trying to build unique actions / functions based on the discrete events.

    By having separate file events this would allow a better programmatic experience.

    As a Box Application Developer I want to be able to receive a unique, webhook events for the following scenarios:

    1. User uploads new file (brand new binary object placed into a Box Folder) - Folder based event (exists: FILE.UPLOADED)
    2. User uploads a new file version - File AND Folder based event (e.g. FILE_NEW.VERSION)
    3. User restores a previous file version - File AND Folder based event (e.g. FILE_RESTORE.VERSION)

    As the owner of an enterprise application that has deep integration in the BOX platform, it is surprising that I have no way to use the Webhooks to monitor files for new versions… more

    6 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 →
    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. Display folder path under file/folder listings

    For example, for a folder "Project 1" several levels down in the Box hierarchy, display the folder path under the folder name:

    Project 1
    All Files > Level 1 > Level 2 > Level 3 > Level 4

    The folder path would be in a font smaller than the folder name and a slightly muted colour compared to the folder name

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

15. Request for Flexible Report Output Naming and Folder Configuration

    We would like to request enhanced flexibility in report output management.
    Specifically:

    1.The ability to assign arbitrary names to report output files
    2.Support for adding dynamic variables (e.g., date) to file names
    3.The ability to specify separate output folders for each report definition

    These enhancements would improve usability and enable more efficient organization and management of report outputs.

    5 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  ·  Admin Reports  ·  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. Provide enterprise configuration of folder metadata cascade

    1. Provide an enterprise configuration option that would allow viewing/editing/adding folder level metadata without also enabling the ability to cascade metadata.
    2. Provide an enterprise configuration option that would limit the ability to initiate cascading metadata to owners and co-owners.
    3. Provide an enterprise configuration option that would limit the ability of a template to be cascaded.
    5 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  ·  Metadata  ·  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. Box Hubs Box AI does not register all the documents added to that Hub

    Box AI does not recognize all the documents in the Box Hub, and seems to recognize old documents that were removed from the Hub. Currently when I ask Box AI what documents are in my Hub it states only 2 documents out of 10 and one of those documents was previously removed.

    5 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

    researching  ·  0 comments  ·  Box AI  ·  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. Ability to customize collaborator privilege

    Want to automate the task of "when the viewer / uploader notices the need to update a particular locked file, ask the editor to confirm and approve the file update"?
    To do this, from the perspective of user permissions, you need collaborator permissions that remove one permission from the viewer / uploader and grant one permission.

    -Collaborator authority that grants manual workflow startup authority to viewer / uploader authority and cannot unlock files.

    By realizing this authority, the following workflow can be automated in combination with Box Relay.

    (1) Lock the approved document managed by the editor.
    (2) The viewer / uploader notices the need to update the file.
    (3) The viewer / uploader starts a manual workflow for the file.
    (4) The information is notified to the editor by Box Relay, and the editor confirms the content and approves the work.
    (5) The file lock is released by Box Relay.
    Box Relay assigns a task to the viewer / uploader that invokes the manual workflow.
    (6) After the work is completed, the viewer / uploader presses the task completion button to proceed with the workflow.
    (7) The editor confirms the contents and approves the file.
    (8) Approved files are locked again by Box relay.

    The above is a specific story, but in general there are only 7 collaborator privileges, so many BOX users may have tasks that they want to perform but cannot. There is a possibility that all can be solved by creating a customizable collaborator privilege that allows each item to be set freely.

    Want to automate the task of "when the viewer / uploader notices the need to update a particular locked file, ask the editor to confirm and approve the file update"?
    To do this, from the perspective of user permissions, you need collaborator permissions that remove one permission from the viewer / uploader and grant one permission.

    -Collaborator authority that grants manual workflow startup authority to viewer / uploader authority and cannot unlock files.

    By realizing this authority, the following workflow can be automated in combination with Box Relay.

    (1) Lock the approved document managed by the editor.
    (2) The viewer… more

    6 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  ·  Users and Groups  ·  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

19. Allow Adobe Bridge to Show BOX Drive Folders/Files (Worked in Previous BOX Version)

    With the update to BOX Drive Version 2.24.208, Adobe Bridge no longer shows BOX folders and Files when opening files in the application. In pervious BOX Drive version, Adobe Bridge showed folders/files, just like any other files – either local or in other cloud applications. HUGE inconvenience to workflow. Please reinstate this functionality.

    5 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  ·  Workflow  ·  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. Improve management of pending invitations via API

    As we continue to build and customize the collaboration mechanism we found it difficult to manage pending invitations. When calling your API api.box.com/2.0/folders<folder_id>/collaborations it returns approved collaborators in the “accessibleby” object but when it return PENDING collaborators the “accessibleby” object is null, but there’s status “pending” on this collaborator. We would imagine it would capture the email address of that pending collaborator. Seeing this is capable in your public domain to show the pending collaborator with an email address would be very useful to create modules to manage pending collaborators (e.g. resending the invitation, update the email address, etc..).

    The temporary solution that was offered:

    1) create our own database to manage and capture external emails that were sent invitation to collaborate

    OR

    2) query the event logs to find those external emails.

    It doesn’t seem to be very efficient for us to adopt these solutions for the interim when BOX’s API already aware of the email value and Box has the mechanism to manage these pending collaborators and move them to approved once they have a profile in Box.com. This will also help reduce traffic and processes if Box can capture this detail in the collaboration dataset.

    As we continue to build and customize the collaboration mechanism we found it difficult to manage pending invitations. When calling your API api.box.com/2.0/folders<folder_id>/collaborations it returns approved collaborators in the “accessibleby” object but when it return PENDING collaborators the “accessibleby” object is null, but there’s status “pending” on this collaborator. We would imagine it would capture the email address of that pending collaborator. Seeing this is capable in your public domain to show the pending collaborator with an email address would be very useful to create modules to manage pending collaborators (e.g. resending the invitation, update the email address,… more

    7 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

    1 comment  ·  Core & Technical Infrastructure  ·  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