182 results found

1. We want to be able to output a log of access to a folder as a report

   We want to prohibit access to folders with each access right more than necessary.
   We want you to add a function that can acquire the access log to the folder as a monitoring method for that.

   supplement:
   We are not considering removing access rights as a way to ban access.
   We strongly hope for this feature as a way to monitor it.

   (Japan)
   各アクセス権限のあるフォルダに対しても、必要以上にアクセスするのは禁止したい。
   そのための監視する方法としてフォルダへのアクセスログを取得できる機能を追加して欲しい。

   補足:
   アクセスを禁止する方法としてアクセス権の削除は検討してません。
   監視する方法として、この機能の実現を強く希望します。

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

2. When moving a file from an external tenant, the collaboration log of the user invited to the moved file is not output.

   If you perform a move operation under the following conditions, the invitation log will not be included in the collaboration report.

   [External Box tenant]
   Folder X User ①: Editor or higher authority
   ∟File Y User ②: Has access authority (regardless of authority)

   When user ① belonging to the company's tenant moves file Y from the above state by move operation
   ⇒ The log that the user ② invited to file Y was invited to the company's tenant is not listed.

   We heard that this behavior is by design.

   When moving a file from an external Box environment, if the access authority of the user invited to the file also moves to the company's tenant, I think that it is necessary to output a report as an invitation operation.

   When conducting an investigation, you should check the user activity report, not the collaboration log.
   The investigation is very time-consuming, so we want it to be refurbished.

   (In Japanese)
   下記の条件で移動操作を行った場合にコラボレーションレポートに招待のログが記載されません。

   [外部のBoxテナント]
   フォルダX ユーザー①：編集者以上の権限
   ∟ファイルY ユーザー ②：アクセス権限あり(権限は問わない)

   上記の状態から自社テナントに所属するユーザー①が移動操作でファイルYを移動させた場合
   ⇒ファイルYに招待されているユーザー②が自社テナントに招待されたログが記載されません。

   この動作は仕様であると伺っています。
   外部のBox環境からファイルを移動してきた際に、ファイルに招待されているユーザーのアクセス権限も自社テナントに移動する場合は、招待の操作としてレポート出力される必要があると思います。

   調査を行う際にコラボレーションログではなく、ユーザーアクティビティレポートにて確認する必要があります。
   調査に非常に手間がかかるため改修を行ってほしいです。

   If you perform a move operation under the following conditions, the invitation log will not be included in the collaboration report.

   [External Box tenant]
   Folder X User ①: Editor or higher authority
   ∟File Y User ②: Has access authority (regardless of authority)

   When user ① belonging to the company's tenant moves file Y from the above state by move operation
   ⇒ The log that the user ② invited to file Y was invited to the company's tenant is not listed.

   We heard that this behavior is by design.

   When moving a file from an external Box environment, if the access… 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  ·  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