This article explains how Lucid's auto-classification feature works for users, based on the configuration defined in the compliance settings of the Lucid admin panel.
If you’re an account owner or document admin looking to set up or manage classification mappings, please refer to the Lucid admin panel: Compliance settings article for configuration guidance.
What is auto-classification?
Auto-classification is a feature that automatically applies a classification level (such as public, internal, confidential, private, etc.) to documents when certain types of sensitive content are detected via our content inspection feature.
This functionality is based on the classification mappings configured by administrators. Once mappings are in place, Lucid checks your content inspection scan results and automatically applies classifications based on your configured mappings.
How mappings work
When sensitive content is detected in a document via content inspection, Lucid uses the auto-classification mappings to determine which classification to apply to the document. If a document contains multiple sensitive content categories, it will be classified based on the highest-priority classification as defined in the classification table. Classifications are listed in priority order, with the highest priority classification at the top
Example:
- GDPR is mapped to private.
- PII is mapped to internal.
- Private is ranked higher than internal in the mapping table.
In this case, if a document contains both PII and GDPR data, it will be automatically classified as private.
User interaction with auto-classified documents
If a user changes the classification to a higher level
If a user manually replaces the auto-assigned classification of a document with a higher-priority one, Lucid will respect the user's action. The document will not be auto-assigned a classification with a lower priority than the current classification, even if detected sensitive content maps to a lower classification.
Example: A document is auto-classified as internal due to the detection of PII. A user manually updates the classification to private.
→ The classification remains private as private is a higher priority than internal.
If a user changes the classification to a lower level
If a user manually changes the classification to a lower-priority level than the auto-assigned classification, Lucid will automatically change to the higher classification the next time the document is re-scanned by content inspection.
Note: After the initial scan, content inspection scans documents only when the document is modified, not when a classification is manually updated without any content modifications.
Example: A document is auto-classified as internal due to the detection of PII. A user manually changes it to public. Later, the document is edited.
→ Lucid re-scans the document and resets the classification to internal.
Behavior when a document is already manually classified
If a document has already been manually classified and sensitive content is later detected, Lucid will only change the classification if the auto-classified level is higher in priority than the existing one.
Example 1: A document is manually classified as public, PII is detected (mapped to internal).
→ Lucid upgrades the classification to internal.
Example 2: A document is manually classified as private, PII is detected (mapped to internal).
→ Lucid does not change the classification, since private is higher than internal in the priority order.
Summary of auto-classification behavior
| Scenario | Outcome |
| Sensitive content is detected and the sensitive category is mapped to a classification. | The document is auto-classified based on configured mappings. |
| Multiple sensitive categories are detected in a single document. The sensitive categories are mapped to different classifications. | The highest-priority classification is applied. |
| A user increases the classification level. | Lucid honors the higher classification and will not move the classification down to the lower priority mapping. |
| A user decreases the classification level. | Lucid reverts to the higher classification upon content modification. |
| A document is already classified at a higher level. | No change—Lucid doesn’t move the classification down in priority level. |
| A document is already classified at a lower level. | Lucid applies the higher mapped classification. |
For questions about implementation or troubleshooting, please contact your account manager or Lucid support.
