The information in this article applies to admins on Dropbox Dash.
Note: It can take up to an hour for items from newly connected apps to show since data updates periodically and not in real time.
If updates still don’t appear after an hour, refresh the page or check your connector’s status in the Apps section.
There are two ways to use policies after you’ve set up your requirements:
When policies run automatic fixes, they only evaluate and act on items with directly added access. Items with inherited permissions are skipped and aren’t actioned on. “Inherited” means access granted from a parent folder rather than directly on the file or folder itself.
This only applies to automations run via a policy. Since no fix is applied, these items won’t be logged in Action history. This aligns collaborator behavior with the previously documented handling of inherited links.
Learn more about inherited permissions.
There are 14 policy cards that can be edited and customized.
Note: The Accounts and Owner filters are currently hidden on the Policies page.
You can also edit an existing policy while reviewing the policy matches. Use the filters in the left side panel to preview what the matches will look like with the changes.
Be sure to click Edit when you’re ready to make changes and Save and close when you’re done.
Notes:
Each policy card has a set automatic fix and can’t be changed.
Tip: You can see the automatic fixes in Action history. To see only automatic fixes, enter “policy-automation” in the Actor filter. You can refine your results by adding additional filters.
Every 24 hours at 8:00 UTC, an email summarizing policy matches that need manual review is sent to admins. The email also has a link to review the matches, and identifies who created the alert.
You can view policy matches by clicking View matches in the alert email or the matches on the policy card. From there, you can manually take action on the matches individually or in bulk.
Note: When a policy is deactivated, alerting and automatic fixes will continue until the start of the next cycle at 8:00 UTC. Policy matches will stay in the queue after deactivation.
You’ll only see policy matches when all the requirements are met. Policies trigger alerts or automations only after every condition is satisfied.
Policies run automatically once per day at 8:00 UTC and can’t be modified.
Actions already queued will complete and appear in Action history. They can’t be stopped or undone.
Note: If an item only has inherited links or inherited collaborators, no policy actions are taken and the item won’t appear in Action history.
Actions are permanently logged in Action history for visibility and auditing and can’t be modified.
Only direct access changes made by a policy are logged. Inherited permissions are skipped and can’t be seen in Action history.
Currently, alerts are only sent through email.
Yes, thanks!
Not really
Let us know how why it didn't help:
Thanks for letting us know!
Thanks for your feedback!