Database Schema

Data Storage Overview

Compliance for Confluence stores information using a few different mechanisms:

SQL Database
Content Properties
Space Properties

The classification level of a page is currently stored on the page itself using a Content Property, this makes it possible for you to use CQL to search for pages that have/haven’t been classified using the built-in Confluence Index - this has several performance advantages, however, this also makes it harder to calculate statistics and run SQL to check on the classification level composition in the sytem.

We’re currently working on moving across the implementation to use SQL to store the data that we currently store in Content Properties, which will improve the scalability of the App and provide better reporting capabilities.

Important SQL Tables

The most useful SQL tables for reporting are as follows:

Table Name	Description
AO_E5C20A_SETTINGS	These are the global settings for Compliance
AO_E5C20A_CLEVEL	These are the classification levels stored in your system
AO_E5C20A_EXTRACTIONS	These are the extractions that have been defined by either you or the system
AO_E5C20A_EXTRACTION_RESULT	These are the extractions that have been detected on all pages in your system. This also stores detections that have been redacted.
AO_E5C20A_AUTOMATION	These are the automation rules in your system

Full Database Schema

Below is the full Database Schema for Compliance for Confluence: