while good in theory, this isn't very practical. in order to make this practical/useful, the following changes should be made :
- communicate the specific criteria used to trigger alerts [what constitutes a 'large' amount of data or 'too many' sign in attempts ? what are the thresholds of 'informational', 'low', 'medium', 'high' ? ...etc.]
- allow admins to configure these values so they're appropriate to their specific use cases. for example, an admin may want to place an especially high priority on the malware alert [which is currently impossible].
- when an admin does make a change to an alert, reflect that change in the control panel. currently, changing the sensitivity of the mass-deletion or mass-move alerts is possible, but the alerts policies page still displays the old severity levels [probably a bug, as revisiting the alert edit page shows the new values].
Hi again @xtolchinskii, I spoke to the team and they have given me a little more info on this. We needed to adjust the calculation which triggers the alerts to deal with anomalies in customers environment, for example to deal with really large files that can each trigger an alert, so we can scale down big files. That is why it is inefficient to translate threshold to specific size or number of files. We found that from our testing this is the most logical way of doing this to allow for the alerts to work intuitively for all teams. Having a strict set of rules for these thresholds for all teams would mean some teams would not have the best experience if they use a much smaller, or much larger amount of data on a daily basis. We feel this approach is more inclusive for all teams, and makes the most sense.
The way we work is changing. Share and discover new ways to work smarter with Dropbox in our community.Sound good? Let's get started.
For more info on available support options, see this article.
If you found the answer to your question, please 'like' the post to say thanks to the user!