diff --git a/images/system/data-privacy/activity-stream-with-deletion-tasks.png b/images/system/data-privacy/activity-stream-with-deletion-tasks.png deleted file mode 100644 index e94a5af1..00000000 Binary files a/images/system/data-privacy/activity-stream-with-deletion-tasks.png and /dev/null differ diff --git a/images/system/data-privacy/creating-a-new-deletion-task.png b/images/system/data-privacy/creating-a-new-deletion-task.png deleted file mode 100644 index f0728751..00000000 Binary files a/images/system/data-privacy/creating-a-new-deletion-task.png and /dev/null differ diff --git a/images/system/data-privacy/data-privacy-deletion-task.png b/images/system/data-privacy/data-privacy-deletion-task.png new file mode 100644 index 00000000..02aa0705 Binary files /dev/null and b/images/system/data-privacy/data-privacy-deletion-task.png differ diff --git a/images/system/data-privacy/data-privacy-task-list.png b/images/system/data-privacy/data-privacy-task-list.png deleted file mode 100644 index 41b8c6cd..00000000 Binary files a/images/system/data-privacy/data-privacy-task-list.png and /dev/null differ diff --git a/images/system/data-privacy/data-privacy-tasks.png b/images/system/data-privacy/data-privacy-tasks.png new file mode 100644 index 00000000..d1721d39 Binary files /dev/null and b/images/system/data-privacy/data-privacy-tasks.png differ diff --git a/images/system/data-privacy/delete-organization-option.png b/images/system/data-privacy/delete-organization-option.png deleted file mode 100644 index 11392a19..00000000 Binary files a/images/system/data-privacy/delete-organization-option.png and /dev/null differ diff --git a/images/system/data-privacy/delete-user-via-data-privacy-panel.gif b/images/system/data-privacy/delete-user-via-data-privacy-panel.gif deleted file mode 100644 index 653811a2..00000000 Binary files a/images/system/data-privacy/delete-user-via-data-privacy-panel.gif and /dev/null differ diff --git a/images/system/data-privacy/delete-user-via-profile.gif b/images/system/data-privacy/delete-user-via-profile.gif deleted file mode 100644 index 632af291..00000000 Binary files a/images/system/data-privacy/delete-user-via-profile.gif and /dev/null differ diff --git a/images/system/data-privacy/delete-user-via-user-panel.gif b/images/system/data-privacy/delete-user-via-user-panel.gif deleted file mode 100644 index f4cbb23e..00000000 Binary files a/images/system/data-privacy/delete-user-via-user-panel.gif and /dev/null differ diff --git a/images/system/data-privacy/deletion-task-activity-stream.png b/images/system/data-privacy/deletion-task-activity-stream.png new file mode 100644 index 00000000..9d9f59bf Binary files /dev/null and b/images/system/data-privacy/deletion-task-activity-stream.png differ diff --git a/images/system/data-privacy/deletion-task-dialog.png b/images/system/data-privacy/deletion-task-dialog.png new file mode 100644 index 00000000..7cc16113 Binary files /dev/null and b/images/system/data-privacy/deletion-task-dialog.png differ diff --git a/images/system/data-privacy/scheduler-deletion-task.png b/images/system/data-privacy/scheduler-deletion-task.png new file mode 100644 index 00000000..fee976ec Binary files /dev/null and b/images/system/data-privacy/scheduler-deletion-task.png differ diff --git a/images/system/data-privacy/user-detail-action-menu.png b/images/system/data-privacy/user-detail-action-menu.png new file mode 100644 index 00000000..bc33bdd2 Binary files /dev/null and b/images/system/data-privacy/user-detail-action-menu.png differ diff --git a/images/system/data-privacy/user-management-action-menu.png b/images/system/data-privacy/user-management-action-menu.png new file mode 100644 index 00000000..385c178e Binary files /dev/null and b/images/system/data-privacy/user-management-action-menu.png differ diff --git a/locale/admin-docs.pot b/locale/admin-docs.pot index 2ffe3549..dcb2c031 100644 --- a/locale/admin-docs.pot +++ b/locale/admin-docs.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Zammad Admin Documentation pre-release\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-07-07 10:58+0200\n" +"POT-Creation-Date: 2025-07-21 11:21+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -19076,208 +19076,251 @@ msgid "Data Privacy" msgstr "" #: ../system/data-privacy.rst:4 -msgid "For compliance with GDPR and other data privacy laws, you can **permanently delete users from the system**, along with **all of their associated tickets**. To access this section, ``admin.data_privacy`` permission is required." +msgid "You can delete users and their tickets by creating a deletion task. This can be required for compliance with GDPR and other data privacy laws. This page describes the places where you can do it, how to do it and includes additional useful information." msgstr "" -#: ../system/data-privacy.rst:8 -msgid "You can create manual deletion tasks or even automated deletion tasks for tickets and users based on custom conditions via :doc:`scheduler `!" +#: ../system/data-privacy.rst:10 +msgid "Important Information" msgstr "" #: ../system/data-privacy.rst:12 -msgid "On older systems that have not been updated yet, customers can also be :docs:`deleted via the Zammad console `." +msgid "The permission ``admin.data_privacy`` is required to initiate a deletion task." msgstr "" -#: ../system/data-privacy.rst:19 -msgid "User deletion dialog in the Data Privacy panel" +#: ../system/data-privacy.rst:13 +msgid "If you want to delete an organization, the deletion task of the last remaining user of this organization asks you if you want to delete the user's organization as well." +msgstr "" + +#: ../system/data-privacy.rst:16 +msgid "It is not possible to only delete a user and keep its tickets." +msgstr "" + +#: ../system/data-privacy.rst:17 +msgid "You can't delete your own account." +msgstr "" + +#: ../system/data-privacy.rst:18 +msgid "You can't delete the system's last remaining administrator account." msgstr "" #: ../system/data-privacy.rst:19 -msgid "The user deletion dialog lists some of the tickets that will be removed from the system along with the user." +msgid "You can create :docs:`data privacy deletion task via API `." msgstr "" -#: ../system/data-privacy.rst:24 -msgid "Deleting Users via GUI" +#: ../system/data-privacy.rst:20 +msgid "Only customer tickets of a user are deleted. If the user is also agent, only the owner gets removed from the affected tickets." msgstr "" -#: ../system/data-privacy.rst:26 -msgid "🔥 **All deletions are FINAL!**" +#: ../system/data-privacy.rst:22 +msgid "All deletions are final! Double check your commands." msgstr "" -#: ../system/data-privacy.rst:28 -msgid "Once you click “Delete”, the action cannot be canceled or undone." +#: ../system/data-privacy.rst:25 +msgid "Manual Deletion via GUI" +msgstr "" + +#: ../system/data-privacy.rst:27 +msgid "You can initiate a data privacy deletion task from different places in Zammad:" +msgstr "" + +#: ../system/data-privacy.rst:29 +msgid "User management" msgstr "" #: ../system/data-privacy.rst:30 -msgid "Any time you delete a user, all their tickets will be deleted, as well. It is not possible to delete a user and still keep their tickets." +msgid "User detail page" msgstr "" -#: ../system/data-privacy.rst:33 -msgid "**The following records cannot be deleted:**" +#: ../system/data-privacy.rst:31 +msgid "Data privacy management" msgstr "" -#: ../system/data-privacy.rst:35 -msgid "Your own account" +#: ../system/data-privacy.rst:33 +msgid "Independent of where you initiate the deletion task, the dialog always looks the same and consists of the following sections:" msgstr "" #: ../system/data-privacy.rst:36 -msgid "The system's last remaining administrator account" +msgid "User: either the user is pre-selected or you can search for a user by typing its name." msgstr "" -#: ../system/data-privacy.rst:39 -msgid "Step 1: Find a User / Confirm Deletion" +#: ../system/data-privacy.rst:38 +msgid "Delete organization: optional; only available if user is last user of the organization." msgstr "" -#: ../system/data-privacy.rst:41 -msgid "There are three ways to access the user deletion dialog:" +#: ../system/data-privacy.rst:40 +msgid "Preview customer tickets: shows a preview of the affected ticket. Be aware that this is just a preview and it may change, depending on the execution time." msgstr "" -#: ../system/data-privacy.rst:48 -msgid "**from the user's profile**" +#: ../system/data-privacy.rst:43 +msgid "Confirmation: this is a safety feature where you have to enter ``DELETE`` manually to make sure you are not deleting data by accident." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog in a user profile" +#: ../system/data-privacy.rst:None +msgid "Screenshot shows the dialog for creating a deletion task." msgstr "" -#: ../system/data-privacy.rst:48 -msgid "Click **Action > Delete**." +#: ../system/data-privacy.rst:51 +msgid "Read on about how to create a deletion task in the different places." msgstr "" -#: ../system/data-privacy.rst:55 -msgid "**in the “Manage > Users” Admin Panel**" +#: ../system/data-privacy.rst:54 +msgid "User Management" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Users” in the Admin Panel" +#: ../system/data-privacy.rst:56 +msgid "To delete a user and its tickets from within the :doc:`user management `, simply locate the user in question (e.g. by searching) and choose **Delete** from the action menu via ︙ button in the user table:" msgstr "" -#: ../system/data-privacy.rst:55 -msgid "Use the **⋮ Actions** menu for the target user." +#: ../system/data-privacy.rst:None +msgid "Screenshot shows a user from user management and the action menu with highlighted sections." msgstr "" -#: ../system/data-privacy.rst:63 -#: ../system/data-privacy.rst:101 -msgid "**in the “System > Data Privacy” Admin Panel**" +#: ../system/data-privacy.rst:67 +msgid "User Detail Screen" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Accessing the user deletion dialog under “Data Privacy” in the Admin Panel" +#: ../system/data-privacy.rst:69 +msgid "To delete a user and its tickets from the user detail screen, choose **Delete** from the action menu in the top right corner:" msgstr "" -#: ../system/data-privacy.rst:62 -msgid "Use the **New Deletion Task** button. Search for users by name or email address." +#: ../system/data-privacy.rst:None +msgid "Screenshot shows an user detail dialog and the action menu with highlighted sections." msgstr "" -#: ../system/data-privacy.rst:76 -msgid "**Delete organizations**" +#: ../system/data-privacy.rst:78 +msgid "Data Privacy Task" msgstr "" -#: ../system/data-privacy.rst:66 -msgid "If the customer you are deleting is the last user in their organization, a **Delete Organization?** option will be displayed in the user deletion dialog:" +#: ../system/data-privacy.rst:80 +msgid "You can find the data privacy section in Zammad's settings under *System > Data Privacy*. To create a deletion task, use the **New Deletion Task** button in the top right corner. The difference to the two mentioned options is that you first have to search the user in the dialog. Everything else is the same." msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Deleting an organization via the user deletion dialog" +#: ../system/data-privacy.rst:None +msgid "Screenshot shows the data privacy section in Zammad's settings with highlighted sections." msgstr "" -#: ../system/data-privacy.rst:75 -msgid "If this option does not appear, make sure there are no pending deletion tasks for other customers from this organization." +#: ../system/data-privacy.rst:91 +msgid "In this section, you can also see logs of scheduled and finished deletion tasks. Read on in the next section to learn more." msgstr "" -#: ../system/data-privacy.rst:79 -msgid "Step 2: Monitor Deletion Job Status" +#: ../system/data-privacy.rst:95 +msgid "Monitor Deletion Jobs" msgstr "" -#: ../system/data-privacy.rst:81 -msgid "It may take up to ten minutes for the system to process your request, so for each user you delete, a “deletion task” is added to the queue. You can keep an eye on the status of these tasks in two places:" +#: ../system/data-privacy.rst:97 +msgid "For each user you delete, a deletion task is added to the deletion queue. It may take up to ten minutes for the system to process your request. Depending on the amount of tickets of the user, the deletion itself can also take some time. You can see status messages of these tasks in two places:" msgstr "" -#: ../system/data-privacy.rst:95 -msgid "**in the Activity Stream**" +#: ../system/data-privacy.rst:102 +msgid "Data privacy management (Zammad's admin settings)" msgstr "" -#: ../system/data-privacy.rst:0 -msgid "Activity Stream showing data privacy tasks" +#: ../system/data-privacy.rst:103 +msgid "Activity stream (by opening the dashboard; deletion task entries only visible for users with ``admin.data_privacy`` permission)" msgstr "" -#: ../system/data-privacy.rst:91 -msgid "For each deleted user, the Activity Stream will be updated twice—once when the task is created, and once when it's complete." +#: ../system/data-privacy.rst:106 +msgid "For each deleted user, you can see two entries: one when the task is created and one when the task has finished." msgstr "" -#: ../system/data-privacy.rst:94 -msgid "These notifications are only visible to users with ``admin.data_privacy`` permissions." +#: ../system/data-privacy.rst:112 +msgid "Activity stream in dashboard" msgstr "" #: ../system/data-privacy.rst:0 -msgid "The task list within Data Privacy shows removals being in progress and completed." +msgid "Screenshot shows the activity stream from Zammad's dashboard with 2 deletion task entries" msgstr "" -#: ../system/data-privacy.rst:104 +#: ../system/data-privacy.rst:118 +msgid "Data privacy management in admin settings" +msgstr "" + +#: ../system/data-privacy.rst:0 +msgid "Screenshot shows the data privacy section in Zammad's settings with a finished and a running task" +msgstr "" + +#: ../system/data-privacy.rst:123 +msgid "Automatic Deletion via Scheduler" +msgstr "" + +#: ../system/data-privacy.rst:125 +msgid "In case you want to automatically clean up old customers with their tickets or specific customers or organizations, you can do this by creating a :doc:`scheduler ` task. Such a scheduler task checks which users are affected based on conditions and runs at pre-defined times and days." +msgstr "" + +#: ../system/data-privacy.rst:130 +msgid "The relevant object is **User** and the action to execute is **Action** > **Add a data privacy deletion task**. You can create a condition to narrow down the users you exactly want to delete. A basic example of a scheduler could look like this:" +msgstr "" + +#: ../system/data-privacy.rst:None +msgid "Screenshot shows important scheduler configuration for a deletion task" +msgstr "" + +#: ../system/data-privacy.rst:140 +msgid "You can delete only tickets if you choose **Ticket** as object in the scheduler task. This gives you an additional action named **Delete immediately** which does exactly that. Customers of these tickets aren't deleted." +msgstr "" + +#: ../system/data-privacy.rst:145 msgid "Frequently Asked Questions" msgstr "" -#: ../system/data-privacy.rst:118 +#: ../system/data-privacy.rst:156 msgid "What happens if I receive an email from a deleted customer?" msgstr "" -#: ../system/data-privacy.rst:107 +#: ../system/data-privacy.rst:148 msgid "Zammad automatically creates a new user account whenever it receives a message from an unrecognized email address, including deleted users. Deleted users are never blocked from creating new tickets." msgstr "" -#: ../system/data-privacy.rst:112 -msgid "In the unlikely event that you receive an email between the time that you click “Delete” and the system has processed your request, **that ticket will be automatically removed**. The ticket number for the lost ticket will be displayed in the Admin Panel under **System > Data Privacy > Completed Tasks > Delete User > Deleted Tickets**." +#: ../system/data-privacy.rst:152 +msgid "In case you receive an email between the time that you click delete and the system has processed your request, that ticket will be automatically **deleted**. The ticket number of the lost ticket is displayed in the data privacy management in Zammad's admin settings in the deletion task entry under **Deleted Tickets**." msgstr "" -#: ../system/data-privacy.rst:127 +#: ../system/data-privacy.rst:162 msgid "What about user information stored in internal notes or other messages?" msgstr "" -#: ../system/data-privacy.rst:121 -msgid "The deletion process removes **user accounts and associated tickets only**." -msgstr "" - -#: ../system/data-privacy.rst:123 -msgid "If there are references to a user's name or information stored elsewhere in the system, that information **will not be removed** because there is no way to safely determine if it actually describes the user in question." +#: ../system/data-privacy.rst:159 +msgid "The deletion process removes user accounts and associated tickets **only**. If there are references to a user's name or information stored somewhere else in the system, this information **will not be removed** because there is no way to safely determine which information is relevant." msgstr "" -#: ../system/data-privacy.rst:134 -msgid "I deleted an user and can still see a message they sent!" +#: ../system/data-privacy.rst:169 +msgid "I deleted a user and can still see a message they sent!" msgstr "" -#: ../system/data-privacy.rst:130 -msgid "Tickets can only belong to a single customer, but may contain messages (“articles”) from many people. If you deleted a user but you're still seeing articles they sent, don't worry—those articles are for a ticket that belongs to someone else, and no longer contain any reference to the sender's identity." +#: ../system/data-privacy.rst:165 +msgid "Tickets can only belong to a single customer, but may contain messages from many people. If you deleted a user but you're still seeing articles they sent, then it is an article in a ticket from another customer. The user information of the deleted user is removed but the articles in question are still available." msgstr "" -#: ../system/data-privacy.rst:138 +#: ../system/data-privacy.rst:173 msgid "I removed a customer, now my reporting is off!" msgstr "" -#: ../system/data-privacy.rst:137 -msgid "When removing users and their tickets, all references are removed. This also affects e.g. Reporting - these information are lost." +#: ../system/data-privacy.rst:172 +msgid "When removing users and their tickets, all references are removed. This also affects reporting - these information are lost." msgstr "" -#: ../system/data-privacy.rst:142 +#: ../system/data-privacy.rst:177 msgid "How long does Zammad store created tasks?" msgstr "" -#: ../system/data-privacy.rst:141 +#: ../system/data-privacy.rst:176 msgid "Please see the on-premise data section of the :docs:`data privacy ` chapter." msgstr "" -#: ../system/data-privacy.rst:147 +#: ../system/data-privacy.rst:182 msgid "What about re-assigned tickets? I want to delete them, too." msgstr "" -#: ../system/data-privacy.rst:145 -msgid "Only tickets assigned to the matching customer at the time of the execution of the data privacy deletion task will be deleted. The deletion will not consider historical assignments." +#: ../system/data-privacy.rst:180 +msgid "Only tickets which are currently assigned to the matching customer at the time of the execution of the data privacy deletion task will be deleted. The deletion will not consider historical assignments." msgstr "" -#: ../system/data-privacy.rst:151 +#: ../system/data-privacy.rst:185 msgid "Why are there so many deletion task entries, I didn't create them!" msgstr "" -#: ../system/data-privacy.rst:150 -msgid "The deletion tasks can come from the :doc:`/manage/scheduler` as well. Namely the action *\"Add a data privacy deletion task\"* is causing the entries." +#: ../system/data-privacy.rst:185 +msgid "The deletion tasks can come from :doc:`scheduler` tasks as well. See :ref:`automatic-deletion-scheduler` above." msgstr "" #: ../system/integrations/checkmk/admin-panel-reference.rst:2 diff --git a/system/data-privacy.rst b/system/data-privacy.rst index dd7faedf..f9df44f7 100644 --- a/system/data-privacy.rst +++ b/system/data-privacy.rst @@ -1,152 +1,186 @@ Data Privacy ============ -For compliance with GDPR and other data privacy laws, you can **permanently -delete users from the system**, along with **all of their associated tickets**. -To access this section, ``admin.data_privacy`` permission is required. - -You can create manual deletion tasks or even automated deletion tasks for -tickets and users based on custom conditions via -:doc:`scheduler `! - -On older systems that have not been updated yet, customers can also be -:docs:`deleted via the Zammad console `. - -.. figure:: /images/system/data-privacy/creating-a-new-deletion-task.png - :alt: User deletion dialog in the Data Privacy panel +You can delete users and their tickets by creating a deletion task. +This can be required for compliance with GDPR and other data privacy laws. This +page describes the places where you can do it, how to do it and includes +additional useful information. + +Important Information +--------------------- + +- The permission ``admin.data_privacy`` is required to initiate a deletion task. +- If you want to delete an organization, the deletion task of the last remaining + user of this organization asks you if you want to delete the user's + organization as well. +- It is not possible to only delete a user and keep its tickets. +- You can't delete your own account. +- You can't delete the system's last remaining administrator account. +- You can create :docs:`data privacy deletion task via API `. +- Only customer tickets of a user are deleted. If the user is also agent, only + the owner gets removed from the affected tickets. +- All deletions are final! Double check your commands. + +Manual Deletion via GUI +----------------------- + +You can initiate a data privacy deletion task from different places in Zammad: + +- User management +- User detail page +- Data privacy management + +Independent of where you initiate the deletion task, the dialog always looks +the same and consists of the following sections: + +- User: either the user is pre-selected or you can search for a user by typing + its name. +- Delete organization: optional; only available if user is last user of the + organization. +- Preview customer tickets: shows a preview of the affected ticket. Be aware + that this is just a preview and it may change, depending on the execution + time. +- Confirmation: this is a safety feature where you have to enter ``DELETE`` + manually to make sure you are not deleting data by accident. + +.. figure:: /images/system/data-privacy/deletion-task-dialog.png + :alt: Screenshot shows the dialog for creating a deletion task. :align: center + :width: 60% - The user deletion dialog lists some of the tickets - that will be removed from the system along with the user. +Read on about how to create a deletion task in the different places. +User Management +^^^^^^^^^^^^^^^ -Deleting Users via GUI ----------------------- +To delete a user and its tickets from within the +:doc:`user management `, simply locate the user in question +(e.g. by searching) and choose **Delete** from the action menu via ︙ button in +the user table: -.. warning:: 🔥 **All deletions are FINAL!** +.. figure:: /images/system/data-privacy/user-management-action-menu.png + :alt: Screenshot shows a user from user management and the action menu with highlighted sections. + :align: center + :width: 80% - Once you click “Delete”, the action cannot be canceled or undone. +User Detail Screen +^^^^^^^^^^^^^^^^^^ - Any time you delete a user, all their tickets will be deleted, as well. - It is not possible to delete a user and still keep their tickets. +To delete a user and its tickets from the user detail screen, choose **Delete** +from the action menu in the top right corner: -.. note:: **The following records cannot be deleted:** +.. figure:: /images/system/data-privacy/user-detail-action-menu.png + :alt: Screenshot shows an user detail dialog and the action menu with highlighted sections. + :align: center + :width: 60% - * Your own account - * The system's last remaining administrator account +Data Privacy Task +^^^^^^^^^^^^^^^^^ -Step 1: Find a User / Confirm Deletion -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +You can find the data privacy section in Zammad's settings under *System > +Data Privacy*. To create a deletion task, use the **New Deletion Task** button +in the top right corner. The difference to the two mentioned options is +that you first have to search the user in the dialog. Everything else is the +same. -There are three ways to access the user deletion dialog: +.. figure:: /images/system/data-privacy/data-privacy-deletion-task.png + :alt: Screenshot shows the data privacy section in Zammad's settings with highlighted sections. + :align: center + :width: 60% -**from the user's profile** - .. figure:: /images/system/data-privacy/delete-user-via-profile.gif - :alt: Accessing the user deletion dialog in a user profile - :align: center +In this section, you can also see logs of scheduled and finished deletion tasks. +Read on in the next section to learn more. - Click **Action > Delete**. +Monitor Deletion Jobs +--------------------- -**in the “Manage > Users” Admin Panel** - .. figure:: /images/system/data-privacy/delete-user-via-user-panel.gif - :alt: Accessing the user deletion dialog under “Users” in the Admin Panel - :align: center +For each user you delete, a deletion task is added to the deletion queue. +It may take up to ten minutes for the system to process your request. Depending +on the amount of tickets of the user, the deletion itself can also take some +time. You can see status messages of these tasks in two places: - Use the **⋮ Actions** menu for the target user. +- Data privacy management (Zammad's admin settings) +- Activity stream (by opening the dashboard; deletion task entries only visible + for users with ``admin.data_privacy`` permission) -**in the “System > Data Privacy” Admin Panel** - .. figure:: /images/system/data-privacy/delete-user-via-data-privacy-panel.gif - :alt: Accessing the user deletion dialog under “Data Privacy” in the Admin Panel - :align: center +For each deleted user, you can see two entries: one when the task is created and +one when the task has finished. - Use the **New Deletion Task** button. Search for users by name or email - address. - -**Delete organizations** - If the customer you are deleting is the last user in their organization, - a **Delete Organization?** option will be displayed in the user deletion - dialog: - - .. figure:: /images/system/data-privacy/delete-organization-option.png - :alt: Deleting an organization via the user deletion dialog +Activity stream in dashboard + .. figure:: /images/system/data-privacy/deletion-task-activity-stream.png + :alt: Screenshot shows the activity stream from Zammad's dashboard with 2 deletion task entries :align: center - :width: 60% - If this option does not appear, make sure there are no pending deletion - tasks for other customers from this organization. +Data privacy management in admin settings + .. figure:: /images/system/data-privacy/data-privacy-tasks.png + :alt: Screenshot shows the data privacy section in Zammad's settings with a finished and a running task + :align: center + :width: 80% -Step 2: Monitor Deletion Job Status -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +.. _automatic-deletion-scheduler: -It may take up to ten minutes for the system to process your request, -so for each user you delete, a “deletion task” is added to the queue. -You can keep an eye on the status of these tasks in two places: +Automatic Deletion via Scheduler +-------------------------------- -**in the Activity Stream** - .. figure:: /images/system/data-privacy/activity-stream-with-deletion-tasks.png - :alt: Activity Stream showing data privacy tasks - :align: center - :width: 90% +In case you want to automatically clean up old customers with their tickets or +specific customers or organizations, you can do this by creating a +:doc:`scheduler ` task. Such a scheduler task checks which +users are affected based on conditions and runs at pre-defined times and days. - For each deleted user, the Activity Stream will be updated twice—once when - the task is created, and once when it's complete. +The relevant object is **User** and the action to execute is **Action** > **Add +a data privacy deletion task**. You can create a condition to narrow down the +users you exactly want to delete. A basic example of a scheduler could look like +this: - .. hint:: These notifications are only visible to users with - ``admin.data_privacy`` permissions. +.. figure:: /images/system/data-privacy/scheduler-deletion-task.png + :alt: Screenshot shows important scheduler configuration for a deletion task + :align: center + :width: 80% -**in the “System > Data Privacy” Admin Panel** - .. figure:: /images/system/data-privacy/data-privacy-task-list.png - :alt: The task list within Data Privacy shows removals being in progress and completed. - :align: center - :width: 90% +You can delete only tickets if you choose **Ticket** as object in the scheduler +task. This gives you an additional action named **Delete immediately** which +does exactly that. Customers of these tickets aren't deleted. Frequently Asked Questions -------------------------- What happens if I receive an email from a deleted customer? - Zammad automatically creates a new user account - whenever it receives a message from an unrecognized email address, - including deleted users. + Zammad automatically creates a new user account whenever it receives a + message from an unrecognized email address, including deleted users. Deleted users are never blocked from creating new tickets. - In the unlikely event that you receive an email - between the time that you click “Delete” - and the system has processed your request, - **that ticket will be automatically removed**. - The ticket number for the lost ticket will be displayed - in the Admin Panel under **System > Data Privacy > - Completed Tasks > Delete User > Deleted Tickets**. + In case you receive an email between the time that you click delete and + the system has processed your request, that ticket will be automatically + **deleted**. The ticket number of the lost ticket is displayed in the data + privacy management in Zammad's admin settings in the deletion task entry + under **Deleted Tickets**. What about user information stored in internal notes or other messages? - The deletion process removes **user accounts and associated tickets only**. - - If there are references to a user's name or information - stored elsewhere in the system, - that information **will not be removed** - because there is no way to safely determine - if it actually describes the user in question. - -I deleted an user and can still see a message they sent! - Tickets can only belong to a single customer, - but may contain messages (“articles”) from many people. - If you deleted a user but you're still seeing articles they sent, - don't worry—those articles are for a ticket that belongs to someone else, - and no longer contain any reference to the sender's identity. + The deletion process removes user accounts and associated tickets **only**. + If there are references to a user's name or information stored somewhere else + in the system, this information **will not be removed** because there is no + way to safely determine which information is relevant. + +I deleted a user and can still see a message they sent! + Tickets can only belong to a single customer, but may contain messages from + many people. If you deleted a user but you're still seeing articles they + sent, then it is an article in a ticket from another customer. The user + information of the deleted user is removed but the articles in question are + still available. I removed a customer, now my reporting is off! - When removing users and their tickets, all references are removed. - This also affects e.g. Reporting - these information are lost. + When removing users and their tickets, all references are removed. This also + affects reporting - these information are lost. How long does Zammad store created tasks? Please see the on-premise data section of the :docs:`data privacy ` chapter. What about re-assigned tickets? I want to delete them, too. - Only tickets assigned to the matching customer at the time of the execution - of the data privacy deletion task will be deleted. The deletion will not - consider historical assignments. + Only tickets which are currently assigned to the matching customer at the + time of the execution of the data privacy deletion task will be deleted. + The deletion will not consider historical assignments. Why are there so many deletion task entries, I didn't create them! - The deletion tasks can come from the :doc:`/manage/scheduler` as well. - Namely the action *"Add a data privacy deletion task"* is causing the - entries. + The deletion tasks can come from :doc:`scheduler` tasks + as well. See :ref:`automatic-deletion-scheduler` above.