For the complete documentation index, see llms.txt. This page is also available as Markdown.

Schemes

Anonymization schemes allow you to define which data categories should be selected by default when working in the stage Anonymization. This means that in repetitive processes, the user does not have to manually set the same categories every time.

The scheme does not affect the operation AI Classification or the scope of detected data. The document is always classified in the standard way, and after moving to the stage Anonymization the system automatically sets the toggles according to the global scheme or the scheme assigned to the project. If the project has its own scheme, it takes precedence over the global setting.

Example 1 – one scheme for the entire organization

The company uses Bluur mainly to anonymize CVs, and in each document it wants to hide the same set of data by default, for example first name, last name, email address, phone number, and address details.

The administrator creates a schema CV and sets it as the global schema. There is no need to assign it separately to each project.

Documents are classified by default. After moving to the stage Anonymization the system automatically sets the category sliders according to the schema CV.

Example 2 – different schemes for different projects

The organization uses Bluur to work with different types of documents, for example resumes and contracts.

The administrator creates separate schemes CV and Contracts. The scheme CV can be set as global, while the scheme assigned to the project intended for handling contracts Contracts.

Documents in the contracts project will use the scheme Contracts, because the scheme assigned to the project takes precedence over the global scheme. The remaining projects without their own scheme will continue to use the scheme CV.

Last updated