What are the limitations on Policies and Automations in Box?

Follow

·

Get Training

The following are certain conditions that might impact your organization's set Policies and Automation:

  • Download activity policies will not be triggered by downloads made through the Box Sync client
  • Files that have violated one of your policies may not be caught before they are downloaded to another user’s computer by the Box Sync client and cannot be deleted by Box Sync if they have been downloaded
  • There is a limit of 10 rules for each policy and a limit of 500 policies for each Enterprise
  • Policies regarding content within a file apply only to the following file types (more file types are being added progressively):

    csv, tsv, doc, dot, docx, gsheet, htm, html, msg, odt, odp, ods, pdf, ppt, pptx, rtf, xhtml, xls, xlsm, xlsx, xml, xsd, xsl, xslt, xhtml, as, as3, asm, bat, c, cc, cmake, cpp, cs, css, cxx, diff, erb, groovy, h, haml, hh, java, js, less, m, make, ml, mm, php, pl, plist, properties, py, rb, sass, scala, script, scm, sml, sql, sh, txt, vi, vim, yaml

  • Upload policies will not be applied to files over 100MB in size
  • Our Policies and Automations engine only scans the first 16MB of a document's extracted text for flagged content (a solution to scan the full text will be released in the upcoming months)
  • Given a particular feature in our API handling, a very small number of files may not have Policy or Automation actions applied to them (this is a very minor edge case and should not affect the majority of files that have Policies or Automations applied to them)
Was this article helpful?
3 out of 4 found this helpful