Skip to content

Life cycles - Overview

admin_lifecycles_overview_v1_de.png

The following life cycles can be administered in this section:

Groups

In OpenOlat Administration, settings for the group lifecycle can be configured. It proceeds in the following steps:

  • Inactivation
  • Deletion
  • Irrevocable deletion

Settings can be made both for groups in general and only for certain group types.

Group lifecycle — Details

Steps and settings for the automatic group lifecycle.
Group lifecycle

To the top of the page ^

Courses

The life cycle of courses can be defined,

  • whether and when a course is automatically set to "Finished" status
  • when it is then moved to the trash,
  • and when it will be permanently deleted

Course owners can be automatically informed of any status changes.

Controlling a running process

A saved change to the lifecycle settings takes effect immediately on a process that is already running: the process re-checks the active configuration before each course. This ensures that changed rules take effect immediately. Using the "Stop process" button, a running pass can additionally be stopped immediately. This way a corrected setting takes effect right away, even when many courses have already been selected for processing.

To the top of the page ^

Account

Similar to the automatically controlled course lifecycle, the lifecycle of OpenOlat users' accounts can also be automated.

Note

The lifecycle runs in separate steps and is fed by partly different settings. The following table provides an overview.

Variant Settings source Mail actions for automations Version
Account expiry a) User Management > Create user (field "Account expiry") or subsequently in the "Account" tab b) Automatically and thus system-wide, configured in Administration. Important: Both paths can be active simultaneously; the one whose time expires first takes precedence. Configurable before and/or after account expiry
Deactivation Automatically: Administration > Life cycles > Account (inactivity period) or Manually: User Management > Users > "Account" tab Configurable before and/or after deactivation
Deletion Automatically: Administration > Life cycles > Account (after deactivation period) or Manually: User Management > Delete user Configurable before and/or after deletion

Note

General rule: If no new login occurs within the specified period, the user account is deleted. Additionally: It can be set up that the irrevocable deletion in the last step takes place automatically or exclusively manually.

Different notifications can be formulated for each step in the context of the steps and the time of the mail notification can be defined.

Deactivation and reactivation

Deactivation sets the account status to "Inactive". The person can no longer log in. The account itself is fully retained. Password, profile, roles, group memberships and course data remain unchanged.

Reactivation sets the account status back to "Active". The person logs in with the existing password. A new password is not required.

You reactivate an account manually under User Management > Select user > "Account" tab. If the person logs in via Shibboleth, OpenOlat reactivates the inactive account automatically.

Only deletion removes data. It also deletes the password irrevocably, see Delete user >.

To the top of the page ^