Soft-deleted users
An administrator soft-deletes an account, for example of an employee who has left, through the provisioning interfaces of the Middleware. The account can no longer sign in, and its data stays until the account is restored or deleted for good. The Middleware documentation describes the procedure in User soft delete; what users see afterwards is described under People who have left the organization.
The UI needs no configuration of its own. Two Middleware properties decide what users can do:
| Property | Default | Effect |
|---|---|---|
com.openexchange.calendar.allowChangeOfOrganizer | false | With true, a participant can take over an appointment whose organizer was soft-deleted if all other participants are internal, and the notice in its details links to Change organizer; com.openexchange.calendar.allowChangeOfOrganizerWithExternals does not lift that condition in the UI. With false, the appointment keeps its organizer until the account is deleted for good, and only participants who were given edit rights can change it. The property also decides whether organizers, and participants they gave edit rights, can hand over appointments whose organizer is still active. |
com.openexchange.user.softDelete.retentionDays | 30 | How many days a soft-deleted account stays before the Middleware deletes it for good. 0 keeps it until an administrator deletes or restores it. |
Both are config-cascade properties. The UI reads com.openexchange.calendar.allowChangeOfOrganizer for the context as io.ox/calendar//chronos/allowChangeOfOrganizer, while the Middleware checks it for the user who changes the organizer. Set it server-wide or per context, not per user: a different value for a single user shows the action where the Middleware refuses it, or hides it where the Middleware would allow it.