Configuration Manager - Audit Log

Include login name as initiator or target name into event for user objects

Includes the login name as name for the initiator and target resources if they are user objects. Attention: this can include sensitive data into the audit log, only enable if login does not include personal data.

Include token for initiator of log event for user objects

Includes the login name as name for the initiator and target resources if they are user objects. Attention: The integration does only work if the forwarding of the external IP address is configured in the system infrastructure.This also does include sensitive data into the audit log.

Include external IP address for initiator resources into events

Enable logging for login and logout processes

Enables the writing of audit log entries for login and logout.

Enable logging for export of user data

Enables the writing of audit log entries for export of user data.

Enable logging for changes to group assignment

Enables the writing of audit log entries for changes on group memberships.

Enable logging for password changes and requests

Enables the writing of audit log entries for changes of the password or requests by a user.

Enable logging for access to reports and exports

Enables the writing of audit log entries for access to reports and export of report results.

Enable logging for system configuration changes

Enables the writing of audit log entries for every file download of script execution in support backend.

Enable logging for support backend executions

Enable logging for data access without access rights (API calls)

Enables logging of audit log entries for access to unauthorised resources(403 access forbidden).

Enable logging for access to dashboard

Enables logging of audit log entries for access to dashboard page(s).

Enable logging of changes of the client administration

Enables logging of audit log entries for changes done to Client Objects.

Enables logging of audit log entries for changes to notifications.

Enables the writing of audit log entries for changes done to a notification

Enable logging for access to system messages (message monitor)

Enables logging of audit log entries for access of messages in system messages.

Enable logging for access to user messages (inbox)

Enables logging of audit log entries for access to user messages (inbox)Metatags

Enable logging for changes on user data (by other user)

Enables the writing of audit log entries for the change of user data.

General logging fur user data change

Log user data changes in general (audit log entry only).

Record user data changes to database table on attribute level

Explicitly log the changed values with reference to the event id in table “audit_log_user_data”.

Enable logging for access rights changes

Access right changes on Objects

Access right changes on Objects

Enables the writing of audit log entries for access right changes on objects, like courses, media, etc.

Access right changes on Navigation Items

Enables the writing of audit log entries for access right changes on navigation entries.

Metatags

Enable logging for external service provider changes

Enables logging of audit log entries for changes to the External service providers.

Enable logging for changes done in the cost centre

Enables logging of audit log entries for changes to the cost centres.

Enable logging for changes done in the Metatag

Enables logging of audit log entries for changes to the metatags.

Enable logging for changes done in the classification

Enables logging of audit log entries for changes to the classifications.

Enable logging for changes done in the provider

Enables logging of audit log entries for changes to the providers.

Validation settings

Validation

When ticked the LMS can become a validated system where certain functions require passwords to be entered when changes are made. This is defined in the ‘Navigation’ function when creating or editing default menus.

E-signature

When ticked the e-signature is active and every change of a validation relevant entity needs to be confirmed by an e-signature. The e-signature for the creation and change of validation relevant elements does not require a username.

Expiration seconds

The Expiration seconds define how long an e-signature is valid for further changes. After the time has expired and a validation relevant element is changes, the user needs to provide a new e-signature.

Secret key

Encryption key used to generate e-Signature tokens.

Initialisation vector

Initialisation value for encryption.