Prevent data export
The data export rule allows you to block the export of data in the spaces and projects, apps, or classification levels covered by a data security policy. What is a data security policy?
This is useful if you need to prevent people from exporting sensitive data to PDF, XML, CSV, and other available formats. The control blocks the export of pages, blog posts, and work items.
Who can do this? |
How do I use this control?
You can choose to prevent or allow data exports for your organization. You can also customize your control with overrides if you wish to be more specific. Apply a default configuration to a policy control
What will my users experience?
The information on this page describes what your users will experience when you apply a control to your organization. If you add overrides, make sure you test the results to ensure the override allows you to maintain the level of security you require. Configure an override for a control
The availability of export or download options varies by app. Users may either find that these options are not visible or receive a notification indicating that their organization has restricted access to these features.
Blocked in Confluence
From a Confluence page, the Export to PDF and Export to Word menu items.
From a Confluence blog, the Export to PDF menu item.
From a Confluence space settings, the options to export to CSV, XML, and PDF.
Blocked in Jira apps
From a work item, the Export to Word, Export to Excel, and Export to XML options.
Export multiple work items (filters, queries) to XML, RSS, Word, HTML, CSV, XLSX.
Blocked in Confluence and Jira apps
If the user attempts to export or download content via a URL or API, the request will return a “can’t export” error.
Limitations
The data export control doesn’t prevent Marketplace or custom apps from exporting content from Confluence or Jira apps.
The data export control doesn’t control (or block) browser-based export or download actions such as print, save, or actions performed by browser extensions.
You can use classification levels to restrict Confluence page exports within a space. When parent pages with restrictive classification levels have child pages without restrictive classification levels, those child pages are included in exports to XML, PDF, and Word formats. However, both the parent pages and the child pages are omitted when exporting to CSV format.
Was this helpful?