Sometimes, you need to check documents that are extremely confidential. You don't want the text being stored in some database somewhere where you have limited control over who can see it. Confidential checking solves this problem. When you enable confidential checking, text from the document is no longer stored in the reporting database or to disk. The only person who has access to the full details of a check is the person who originally checked the document.
Confidential Checking Is Different From Anonymous Checking
Acrolinx has a privacy-related feature that is sometimes referred to as anonymous checking. It's easy to get these features confused, so it's important to remember the following differences.
- Confidential checking is designed to protect sensitive content.
You can't tell what kind of content was checked but you can still see who ran the check.
- Anonymous checking is designed to protect sensitive user data
You can't tell who ran the check but you can still see what kind of content they checked.
Enable Confidential Checking
Confidential checking is enabled in Content Profiles, so make sure that your Content Profiles are set up to detect confidential documents. For more information about how to set up Content Profiles correctly, see the "Content Profiles" section.
To enable confidential checking, follow these steps:
Create a Content Profile or open an existing Content Profile.
Select the option Check all content confidentially.
Your changes take effect immediately.
What Happens After Confidential Checking Is Enabled
The new checking behavior is easy to observe if you use the Content Analyzer.
Suppose that you check a directory that contains confidential documents only. You won't see any checking statistics when you open the Content Analysis Dashboard. This is because statistics about confidential documents aren't written to the reporting database.
If you check a directory that contains a mixture of confidential and non-confidential documents, the Content Analysis Dashboard only shows statistics for the non-confidential documents.
Generally, this means that confidential documents don’t affect your company quality statistics at all. For example, suppose that you check a high volume of confidential content that contains too many long sentences. If you've been tracking average number of long sentences in your content, you won't see any fluctuation in the average. Even aggregated quality statistics aren’t stored for confidential documents.
Some details about confidential content are still stored on the Core Platform.
|The document path, file name, and custom fields.||Reporting database|
The document path and file name are still written to the reporting database.
We also store general information about each checked document including any custom field that you might have configured, such as "project" or "team".
|Document path and file name.||Log file||The log file contains the file name and path of a checked document, including after a confidential check.|