Anonymous
My feedback
22 results found
-
34 votes
We are conducting user feedback sessions to gather more information
Anonymous supported this idea · -
6 votesAnonymous supported this idea ·
-
37 votesAnonymous supported this idea ·
-
121 votesAnonymous supported this idea ·
-
17 votesAnonymous supported this idea ·
-
24 votesAnonymous supported this idea ·
-
3 votesAnonymous supported this idea ·
-
14 votesAnonymous supported this idea ·
-
25 votes
This is a great feature suggestion, and we plan to add it to the roadmap in the longer term
Anonymous supported this idea · -
39 votesAnonymous supported this idea ·
-
1 voteAnonymous shared this idea ·
-
392 votesAnonymous supported this idea ·
-
213 votes
We currently do not have this planned on our roadmap. Please keep the feedback & use cases coming to help us prioritize this in the future!
Anonymous supported this idea · -
182 votesAnonymous supported this idea ·
-
68 votes
This is still on the roadmap.
Anonymous supported this idea · -
18 votesAnonymous supported this idea ·
-
336 votes
We are currently not planning to implement this feature and will continue to prevent all Box Drive results from appearing in Explorer/Finder searches.
Box Drive does not download the all of the metadata (File name, folder structure, etc.) of your Box content. Instead, it is downloaded on demand and then evicted when it is no longer relevant. This eviction process is not visible to users and it is not easily predictable. This would cause the search results in Explorer/Finder to be inconsistent for users – sometimes they would find a file and other times they may not if the metadata and file were evicted.
We have chosen not to download all of the metadata (and then keep it up to date with changes) as this can result in a large performance, storage and bandwidth tax which is not scalable – especially in environments where users interface with millions of files/folders.
…
Anonymous supported this idea · -
25 votesAnonymous supported this idea ·
-
13 votes
An error occurred while saving the comment Anonymous supported this idea · -
12 votesAnonymous shared this idea ·
Currently, when a manual start workflow is kicked off, an external user can only be selected as a collaborator for a workflow step if they have been set up as an external user previously (i.e. shows up in the "External Users" tab of the "Admin Console- Users and Groups" . This is inconvenient for users who manually start the workflow in cases where this is the first time the external user has been collaborated to anything within an enterprise's Box account. For example, one customer's HR team is starting a workflow for new employee onboarding. At the start of this process, it's very likely the new employee either does not have a Box account or has not shared/collaborated with the enterprise before. In order to add that user to a workflow as a collaborator for the folder created in the workflow, you would need to invite them to a folder prior to starting the workflow (which adds additional manual steps and is not intuitive).
I would like to request for when a manual start workflow is initiated, that the workflow initiator can include any Box user account as a collaborator to be added during the workflow. The user should not have to be previously set up as an external user with that enterprise.