With the upcoming report scheduling function, coupled with improved filters to better streamline reports that are generated, it would be really useful to be able to define a custom save location for a report that is generated as part of that process (i.e. to any folder within your box instance and not just the default 'reports' bucket).

Our use case is that we'd like to set up a series of scheduled reports (soon possible!), each one filtered to activities within a specific folder (also now possible!) and then have that report automatically save into the folder to which it relates (not currently possible). This way, it will be possible for co-owners of a folder to see (saved automatically to their folder) a regularly updated report on some aspect of their folder. In our case, we'd like to do a collaborator report so that we can regularly audit who has access to items within high-level folder trees where each high-level folder contains a LOT of sub-folders and files, and where we have equally a LOT of these high-level folders.

There are several functions within the Admin Console that are only accessible to the primary admin. Setting up SSO for example requires the primary admin, and co-admins are unable to integrate with SSO. In many environments there will not be a single administrator with privileged access across multiple systems, which means the primary admin role will need to be assigned and re-assigned multiple times to perform necessary tasks.

To promote a secure environment where tasks may need to be performed by multiple administrators, I would request either 1) admin console allow for multiple users in the primary admin role, or 2) the co-admin role be empowered to perform necessary tasks without becoming the primary admin.

We strongly request the improvement of the display specification when the log of copying an item to an external tenant's folder is output to the report.

In the current specification, when the destination folder is an external tenant, the report only shows the copied file as "External File".
In other words, we can determine "who" copied "when" and "some file," but we cannot determine "where" and "what" was copied.

We believe this is a major problem in monitoring and preventing information leaks.
I thought it was one of Box's great strengths that most of the operation logs are stored and can be checked, but I never imagined that this very important log would be output in an inadequate form.

Also adding to the problem was the fact that Box Shield's classification labels do not control operations after copying to an external folder.
Currently, the only effective solution is to use Box Govenrnance's linkage restriction feature to block external invitations.
I hope this will be remedied as soon as possible as it interferes with many transactions.

I would like to see a fix for the error that occurs when a group administrator displays a report.

If you try to view the report as a group administrator, you may get the error message [Unexpected error.] error may occur.
The current workaround is to run a report.
We use the report function when we need to take immediate action for recovery, but if we use [Run], which takes a long time to output, the action will be delayed, which is a problem for our business.
Therefore, we request that the function of displaying reports be migrated to the new platform and that the reports be modified so that they can be used correctly.

グループ管理者でのレポート表示操作がエラーとなる事象を改修して欲しい

グループ管理者でレポートの表示を行うと[予期せぬエラーです。]というエラーが発生する場合があります。
現在の回避方法としてはレポートを実行することです。
早急な復旧対応が必要になった際にレポート機能を使用しますが、
出力に時間がかかる[実行]では対応が遅れてしまい業務上問題があります。
そのため、レポートの表示機能を新プラットフォームへの移行、レポートの表示が正しく利用できるように改修を要望します。

I have a use case where I have my Marketing Manager setup as a Co-Admin with permissions to edit metadata templates. We'd now like her to also be able to manage the groups that controls access to marketing's folders. The problem is, because she's a co-admin Box won't allow us to assign her as a group admin. The only way we can allow her to admin the groups is to also give her Manage Groups access as part of her co-admin role. The issue with that is it would give her the ability to manage all groups, which we do not want.

It would be great if the co-admin functionality would allow us to select a list of groups that the co-admin can manage OR make it so that co-admins that don't have permissions to manage groups could also be assigned the Group Admin role.