Content classification

2. 1. Basic principles

Jalios offers you different ways of managing rights on your platform. Community confidentiality and folder rights are powerful mechanisms, but managed locally, on spaces or content.

For organizations handling sensitive content, it is important to have a global, centralized tool for the standardized classification of platform content.

The classification functionality offers 4 different levels:

3. 2. Level 1: Display of classification level

3.1. 2.1 Concept:

The first level consists in informing members of the sensitivity of a content item or of the community in which they find themselves.

In concrete terms, this translates into colored dots indicating the level:

3.1.1. 2.1.1 On content

You'll be able to hover over a description of the implications of the classification level in question.

3.1.2. 2.1.2 On communities

The classification level of a community determines its minimum accreditation level. A community with a secret level won't be able to offer content that's just restricted, or public.

3.2. 2.2 How to set it up :

To activate content classification on your platform, go to your administrator role in the site settings application.

There's a dedicated Classification section, so just click on "Activate classification..." to take advantage of this feature.

All that remains is to define your minimum levels for the communities and spaces concerned in the possible settings menu:

Here you can set the default confidentiality level for platform content. Above all, you can set the minimum level, so as not to allow content to be posted with lower rights than expected.

You'll need to do the same for sub-sites in administration:

4. 3. Level 2: Member authorization

4.1. 3.1 Concept:

If you wish, you can activate a higher level of security by enabling authorization control. This means that, beyond the display of confidentiality levels, each user will be restricted to viewing content equal to or lower than his or her level.

Once this feature has been activated, it is necessary to define user authorization levels.

4.2. 3.2 Set up :

To add this control, simply check the"Member authorization control" box on the"Advanced" tab.

5. 4. Level 3: Functionality control

5.1. 4.1 Concept:

Depending on your information system, and your various integrations, it may be necessary to restrict certain functionalities beyond a certain level of criticality.

To avoid disappointment or misinterpretation by your members, you can activate functionality control.

In this way, you can restrict actions according to the level of confidentiality. The list of features that can be "bridled" depends on the active features on your platforms.

By default, the features that are candidates for bridging are :

• Download button
• Version history
• Print
• Public link
• Share
• Share in another space
• Add or remove a document from JDrive (For people authorized to use this feature)
• Editing a document with JDrive (For people authorized to use this feature)
• Modifying a document with Microsoft 365
• Editing a document with OnlyOffice
• Invitation to edit a document with OnlyOffice

5.2. 4.2 Setting up :

5.3. 4.3

The list of features depends on your configuration. Subscribed options automatically populate the list in the"Features" tab.

6. 5. Level 4: Applying constraints

6.1. 5.1 Concept:

To ensure optimum security, it is possible to impose constraints on your highest levels. It is now possible to impose an access code, or double authentication, to access sensitive content.

By default, without any further integration on your part, the following options are available:

• Mandatory access code for public links
• File download logging
• Mandatory reader tracking

6.2. 5.2 Implementation:

Constraints are set in the tab of the same name. The list may vary according to your configuration. For example, if dual authentication is available on your instance, a corresponding entry allowing you to impose this condition will be proposed.