Set up security levels

To restrict access to all documents for all users, access can be restricted using security levels. The "ECM user" must have a higher security level than the document to view it.

Setting up the ECM document definition

The security level must be passed in the ECM document definition line; in this example, we pull the security level from the document category.

The following fields must be filled in:

1. Type: Variable

2. Source field ID: DOCUMNET CATEGOREY

3. Parameters: SECURITYLEVEL

4. Journal/Entry field number: 81 (Security level)

5. [Optional] ECM Repository/Library field ID: SecurityLevel (Adaptive)

Setting up document category

In this example, we use the security level of the document category, so we enter a value here:

Setting up ECM users

The BC user must be mapped 1-to-1 to an "ECM user," and a security level greater than or equal to the document must be stored in this user so that the user can view the documents. If the security level is lower, the documents will not be displayed to the user:

ECM Setup Matrix / Vertical Solutions

A mapping code must be entered in the "Access Right ECM Entry" field. This mapping code validates the display in the FactBox and when the document is accessed. This mapping code is called before a document is displayed. By default, the code "SECURITY LEVEL DOC ENTRY" is delivered, which checks the document's security level (if this is 0, the document category's security level is used) against the security level of the "ECM User":

If a different test is required, you can create your own mapping codes using the AL code and enter them here.

FactBox and document entry view

In the “ECM Documents” (Buffer) FactBox, the document entry is no longer visible because it is filtered out:

The items are still visible on the “ECM Document Entries” page, but if the security level is not sufficient, the user will receive an error message when retrieving information from the archive: