From 933c4de881d3a9d47d3dd46a663f013477621caf Mon Sep 17 00:00:00 2001 From: ralf401 Date: Fri, 15 Nov 2024 08:33:27 +0100 Subject: [PATCH] Fixes #704 - Added description for inactive state for some features --- locale/admin-docs.pot | 227 ++++++++++++++++++++----------------- manage/groups/settings.rst | 19 +++- manage/roles/index.rst | 6 + manage/time-accounting.rst | 3 +- manage/users/index.rst | 10 +- 5 files changed, 150 insertions(+), 115 deletions(-) diff --git a/locale/admin-docs.pot b/locale/admin-docs.pot index 0325f312..20d5c420 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: 2024-11-13 10:33+0100\n" +"POT-Creation-Date: 2024-11-14 11:32+0100\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -311,7 +311,7 @@ msgstr "" #: ../channels/form.rst:20 #: ../channels/email/accounts/secondary-addresses.rst:35 #: ../channels/email/accounts/secondary-addresses.rst:35 -#: ../manage/groups/settings.rst:82 +#: ../manage/groups/settings.rst:84 #: ../system/objects/types.rst:154 msgid "Email" msgstr "" @@ -969,7 +969,7 @@ msgstr "" #: ../channels/email/accounts/secondary-addresses.rst:41 #: ../channels/email/accounts/secondary-addresses.rst:42 #: ../channels/email/accounts/secondary-addresses.rst:42 -#: ../manage/groups/settings.rst:99 +#: ../manage/groups/settings.rst:101 #: ../manage/macros/how-do-they-work.rst:0 #: ../manage/macros/learn-by-example.rst:0 #: ../manage/roles/admin-permissions.rst:40 @@ -2629,7 +2629,7 @@ msgid "The fields provided by the form are limited to the following:" msgstr "" #: ../channels/form.rst:19 -#: ../manage/groups/settings.rst:14 +#: ../manage/groups/settings.rst:16 #: ../manage/scheduler.rst:39 #: ../manage/slas/how-do-they-work.rst:26 #: ../manage/templates.rst:33 @@ -2661,9 +2661,10 @@ msgid "Zammad comes with certain settings for forms." msgstr "" #: ../channels/form.rst:37 -#: ../manage/groups/settings.rst:115 +#: ../manage/groups/settings.rst:122 #: ../manage/macros/how-do-they-work.rst:0 #: ../manage/overviews.rst:0 +#: ../manage/roles/index.rst:128 #: ../manage/scheduler.rst:111 #: ../manage/templates.rst:43 #: ../manage/webhook/add.rst:123 @@ -5392,7 +5393,7 @@ msgid "The checklist feature is currently a standalone feature. That means you c msgstr "" #: ../manage/groups/access-levels.rst:2 -#: ../manage/users/index.rst:168 +#: ../manage/users/index.rst:172 msgid "Group Permissions" msgstr "" @@ -5646,164 +5647,172 @@ msgstr "" msgid "No matter if you're going to edit or create a new group, each group comes with the following settings you can adjust as needed." msgstr "" -#: ../manage/groups/settings.rst:13 +#: ../manage/groups/settings.rst:12 +msgid "Please note that groups cannot be removed." +msgstr "" + +#: ../manage/groups/settings.rst:15 msgid "This is the name your agents (and customers when using :doc:`/channels/web`) will see within the Zammad-UI." msgstr "" -#: ../manage/groups/settings.rst:32 +#: ../manage/groups/settings.rst:34 msgid "Parent group" msgstr "" -#: ../manage/groups/settings.rst:17 +#: ../manage/groups/settings.rst:19 msgid "You can define *another* group as a parent group here. This is useful if you want to create group hierarchies. In such a hierarchy (child/parent relation), the tree of the parent group is inherited to the child group. That means if you move a group which itself has child groups, the child groups are \"moved\" accordingly. However, there is no inheritance of membership or permissions. That means you can treat each group as an individual group - even if they have a child/parent relation." msgstr "" -#: ../manage/groups/settings.rst:25 +#: ../manage/groups/settings.rst:27 msgid "Zammad doesn't show you any child group of the currently selected group. This would lead to a circular reference!" msgstr "" -#: ../manage/groups/settings.rst:28 +#: ../manage/groups/settings.rst:30 msgid "Zammad supports 10 levels of hierarchy for groups on PostgreSQL systems. If you are using a MySQL database, it is limited to 6 levels. In case you are using MySQL, you should consider to migrate your database anyway (see :docs:`here ` for more information). MySQL will be deprecated with Zammad 7." msgstr "" -#: ../manage/groups/settings.rst:37 +#: ../manage/groups/settings.rst:39 msgid "Assignment timeout" msgstr "" -#: ../manage/groups/settings.rst:35 +#: ../manage/groups/settings.rst:37 msgid "The time in minutes after which the ticket's ownership will revert back to *unassigned* after the assigned agent hasn't worked on the ticket. This timeout does *not* take any working hours in account." msgstr "" -#: ../manage/groups/settings.rst:57 +#: ../manage/groups/settings.rst:59 msgid "Follow-up possible" msgstr "" -#: ../manage/groups/settings.rst:40 +#: ../manage/groups/settings.rst:42 msgid "This option allows you to decide how Zammad should react if a customer replies to a closed ticket (no matter if by e.g. email or UI)." msgstr "" -#: ../manage/groups/settings.rst:44 -#: ../manage/groups/settings.rst:65 +#: ../manage/groups/settings.rst:46 +#: ../manage/groups/settings.rst:67 #: ../misc/object-conditions/basics.rst:108 #: ../misc/object-conditions/basics.rst:123 msgid "yes" msgstr "" -#: ../manage/groups/settings.rst:44 +#: ../manage/groups/settings.rst:46 msgid "The ticket will be reopened. This is the default value." msgstr "" -#: ../manage/groups/settings.rst:48 +#: ../manage/groups/settings.rst:50 msgid "do not reopen Ticket but create new Ticket" msgstr "" -#: ../manage/groups/settings.rst:47 +#: ../manage/groups/settings.rst:49 msgid "The ticket will remain closed and Zammad will create a new ticket instead. The new ticket contains the customers reply only." msgstr "" -#: ../manage/groups/settings.rst:57 +#: ../manage/groups/settings.rst:59 msgid "do not reopen ticket after certain time but create new ticket" msgstr "" -#: ../manage/groups/settings.rst:51 +#: ../manage/groups/settings.rst:53 msgid "The ticket can be reopened unless the specified number of days *after last ticket closure* has been exceeded. If the time limit is exceeded, Zammad will create a new ticket instead of reopening." msgstr "" -#: ../manage/groups/settings.rst:55 +#: ../manage/groups/settings.rst:57 msgid "Choosing this option will provide the option *Reopening time in days* which requires you to provide the number of days you want Zammad to wait until it creates new tickets." msgstr "" -#: ../manage/groups/settings.rst:68 +#: ../manage/groups/settings.rst:70 msgid "Assign follow-ups" msgstr "" -#: ../manage/groups/settings.rst:60 +#: ../manage/groups/settings.rst:62 msgid "This setting allows you to decide if, upon a reopen of a ticket, the last assigned owner should stay assigned or if Zammad should reset the owner to nobody." msgstr "" -#: ../manage/groups/settings.rst:65 +#: ../manage/groups/settings.rst:67 msgid "The ticket will remain with the last agent who owned it. This is the default value." msgstr "" -#: ../manage/groups/settings.rst:68 +#: ../manage/groups/settings.rst:70 #: ../misc/object-conditions/basics.rst:109 #: ../misc/object-conditions/basics.rst:124 msgid "no" msgstr "" -#: ../manage/groups/settings.rst:68 +#: ../manage/groups/settings.rst:70 msgid "The owner assignment of the ticket will be removed." msgstr "" -#: ../manage/groups/settings.rst:71 +#: ../manage/groups/settings.rst:73 msgid "Select which sender's email address Zammad will use outbound for replying on a ticket in this group." msgstr "" -#: ../manage/groups/settings.rst:74 +#: ../manage/groups/settings.rst:76 msgid "**You don't have an email address configured yet?**" msgstr "" -#: ../manage/groups/settings.rst:76 +#: ../manage/groups/settings.rst:78 msgid "Please configure an email based channel before here" msgstr "" -#: ../manage/groups/settings.rst:78 +#: ../manage/groups/settings.rst:80 msgid ":doc:`Channels → Email `" msgstr "" -#: ../manage/groups/settings.rst:79 +#: ../manage/groups/settings.rst:81 msgid ":doc:`Channels → Microsoft 365 `" msgstr "" -#: ../manage/groups/settings.rst:80 +#: ../manage/groups/settings.rst:82 msgid ":doc:`Channels → Google `" msgstr "" -#: ../manage/groups/settings.rst:82 +#: ../manage/groups/settings.rst:84 msgid "and come back afterwards." msgstr "" -#: ../manage/groups/settings.rst:87 +#: ../manage/groups/settings.rst:89 msgid "Signature" msgstr "" -#: ../manage/groups/settings.rst:85 +#: ../manage/groups/settings.rst:87 msgid "Choose which :doc:`signature ` to use when replying to tickets in this group. Leaving this option unset will send emails without any signature." msgstr "" -#: ../manage/groups/settings.rst:95 +#: ../manage/groups/settings.rst:97 msgid "Shared Drafts" msgstr "" -#: ../manage/groups/settings.rst:90 +#: ../manage/groups/settings.rst:92 msgid "Shared drafts allows your agents to share ticket drafts (for new and existing tickets) with their colleagues. By default this setting is enabled, disable it if you don't want your agents to use this function." msgstr "" -#: ../manage/groups/settings.rst:94 +#: ../manage/groups/settings.rst:96 msgid "Learn more about shared drafts :user-docs:`in our user documentation `." msgstr "" -#: ../manage/groups/settings.rst:98 +#: ../manage/groups/settings.rst:100 msgid "An internal note about the group that is only visible to people who can access the group management area." msgstr "" -#: ../manage/groups/settings.rst:102 -msgid "Don't need the group any more? If you can't or don't want to recycle (rename) the group, you can also set it to inactive. Agents and customers will no longer be able to see the group and thus can't add, update or read it's tickets." +#: ../manage/groups/settings.rst:104 +msgid "Don't need the group anymore? If you can't or don't want to recycle (rename) the group, you can also set it to inactive. Agents will no longer be able to see or edit tickets in this group. However, customers can still interact with their existing tickets in an inactive group." +msgstr "" + +#: ../manage/groups/settings.rst:111 +msgid "Want to handle tickets from an inactive group, which are updated by customers?" msgstr "" -#: ../manage/groups/settings.rst:109 -msgid "Currently, groups cannot be removed." +#: ../manage/groups/settings.rst:114 +msgid "You could e.g. create a trigger which moves them to another group when they got updated. Create this trigger before deactivating the group so it is selectable in the trigger configuration." msgstr "" -#: ../manage/groups/settings.rst:113 +#: ../manage/groups/settings.rst:120 msgid "Please keep in mind that you still can route tickets into these groups. This is potentially dangerous, make sure the group is no longer part of email filters or a destination group." msgstr "" -#: ../manage/groups/settings.rst:122 +#: ../manage/groups/settings.rst:129 msgid "Screenshot showing how a group configuration can look like." msgstr "" -#: ../manage/groups/settings.rst:122 +#: ../manage/groups/settings.rst:129 msgid "A sample configuration of a group." msgstr "" @@ -6025,8 +6034,8 @@ msgstr "" #: ../manage/knowledge-base.rst:146 #: ../manage/public-links.rst:39 -#: ../manage/time-accounting.rst:150 -#: ../manage/time-accounting.rst:164 +#: ../manage/time-accounting.rst:151 +#: ../manage/time-accounting.rst:165 #: ../system/maintenance.rst:31 msgid "Title" msgstr "" @@ -6540,7 +6549,7 @@ msgid "You can! To learn more, see :doc:`/system/objects`." msgstr "" #: ../manage/organizations/index.rst:137 -#: ../manage/users/index.rst:144 +#: ../manage/users/index.rst:148 msgid "▶️ Active" msgstr "" @@ -7838,7 +7847,7 @@ msgid "To make it work, you need two separate roles: one with ``ticket.agent`` a msgstr "" #: ../manage/roles/index.rst:2 -#: ../manage/users/index.rst:149 +#: ../manage/users/index.rst:153 msgid "Roles" msgstr "" @@ -7974,7 +7983,7 @@ msgstr "" msgid "Role Details" msgstr "" -#: ../manage/roles/index.rst:122 +#: ../manage/roles/index.rst:123 msgid "Default at Signup" msgstr "" @@ -7994,6 +8003,10 @@ msgstr "" msgid "🙅 **Default roles should never provide admin/agent permissions.**" msgstr "" +#: ../manage/roles/index.rst:126 +msgid "Roles can't be deleted but set to inactive. If you do so, all users loose the permissions of this role. If this inactive role is the only one of a user, this account isn't able to do anything in Zammad. The login is still possible." +msgstr "" + #: ../manage/roles/user-preferences-permissions.rst:2 msgid "User Preferences Permissions" msgstr "" @@ -9223,34 +9236,34 @@ msgid "Additionally, a column with an associated activity type will be rendered msgstr "" #: ../manage/time-accounting.rst:95 -msgid "You can manage available activity types in this screen like any other Zammad object. Only active types will be available for the selection when recording new times." +msgid "You can manage available activity types in this screen like any other Zammad object. Only active types will be available for the selection when recording new times. If an activity type has accounted time, it is still displayed in tickets and included in the accounted time overview." msgstr "" #: ../manage/time-accounting.rst:None msgid "New Time Accounting Activity Type Dialog" msgstr "" -#: ../manage/time-accounting.rst:103 +#: ../manage/time-accounting.rst:104 msgid "Activity types can be set as default, and in that case they will be pre-selected for the agents when they are asked to account their time. It is also possible to unset default activity type, in which case no type will be pre-selected and the agents can make their choice." msgstr "" -#: ../manage/time-accounting.rst:109 +#: ../manage/time-accounting.rst:110 msgid "Accounted Time" msgstr "" -#: ../manage/time-accounting.rst:111 +#: ../manage/time-accounting.rst:112 msgid "Under the **Accounted Time** tab, Zammad provides a section for reviewing all accounted times for your tickets. Accounted times are displayed per years and months." msgstr "" -#: ../manage/time-accounting.rst:115 +#: ../manage/time-accounting.rst:116 msgid "If you have tickets that are overlapping several months, you can differentiate by *time units* and *time units total* (e.g. to allow partial billing) in the downloaded file." msgstr "" -#: ../manage/time-accounting.rst:126 +#: ../manage/time-accounting.rst:127 msgid "Select the right month" msgstr "" -#: ../manage/time-accounting.rst:120 +#: ../manage/time-accounting.rst:121 msgid "Usually you want to bill accounted time of other months than the current one. Just select the relevant year and month to receive the accounted times and ticket information." msgstr "" @@ -9258,81 +9271,81 @@ msgstr "" msgid "Screenshot showing a selection for year and month on time accounting" msgstr "" -#: ../manage/time-accounting.rst:196 +#: ../manage/time-accounting.rst:197 msgid "Tickets and their accounted time" msgstr "" -#: ../manage/time-accounting.rst:129 +#: ../manage/time-accounting.rst:130 msgid "Zammad allows you to receive the accounted information just like you need them. For this you currently have four options to review and also download the relevant data as CSV." msgstr "" -#: ../manage/time-accounting.rst:133 +#: ../manage/time-accounting.rst:134 msgid "To download the CSV data, use the download button right next to each heading (e.g. \"Ticket\")." msgstr "" -#: ../manage/time-accounting.rst:136 +#: ../manage/time-accounting.rst:137 msgid "This can also be automated with API calls." msgstr "" -#: ../manage/time-accounting.rst:139 +#: ../manage/time-accounting.rst:140 msgid "Only the first 20 entries are shown for each table. To see all of them, simply download the records in CSV." msgstr "" -#: ../manage/time-accounting.rst:156 +#: ../manage/time-accounting.rst:157 msgid "Activity" msgstr "" -#: ../manage/time-accounting.rst:143 +#: ../manage/time-accounting.rst:144 msgid "This filter works similar to the ticket filter, with one exception: You'll find each *individual* time accounting step of your agents. This is what you'd also see in the ticket's history before Zammad 5.2." msgstr "" -#: ../manage/time-accounting.rst:147 -#: ../manage/time-accounting.rst:161 -#: ../manage/time-accounting.rst:178 +#: ../manage/time-accounting.rst:148 +#: ../manage/time-accounting.rst:162 +#: ../manage/time-accounting.rst:179 msgid "In this list you'll see the following ticket information:" msgstr "" -#: ../manage/time-accounting.rst:149 -#: ../manage/time-accounting.rst:163 +#: ../manage/time-accounting.rst:150 +#: ../manage/time-accounting.rst:164 #: ../settings/ticket.rst:91 msgid "Number" msgstr "" -#: ../manage/time-accounting.rst:151 -#: ../manage/time-accounting.rst:165 -#: ../manage/time-accounting.rst:182 -#: ../manage/time-accounting.rst:180 +#: ../manage/time-accounting.rst:152 +#: ../manage/time-accounting.rst:166 +#: ../manage/time-accounting.rst:183 +#: ../manage/time-accounting.rst:181 #: ../misc/object-conditions/basics.rst:36 #: ../misc/object-conditions/basics.rst:90 #: ../misc/object-conditions/basics.rst:158 msgid "Customer" msgstr "" -#: ../manage/time-accounting.rst:152 -#: ../manage/time-accounting.rst:166 -#: ../manage/time-accounting.rst:181 +#: ../manage/time-accounting.rst:153 +#: ../manage/time-accounting.rst:167 +#: ../manage/time-accounting.rst:182 msgid "Organization of customer (if applicable)" msgstr "" -#: ../manage/time-accounting.rst:153 +#: ../manage/time-accounting.rst:154 msgid "Agent that accounted the time" msgstr "" -#: ../manage/time-accounting.rst:154 +#: ../manage/time-accounting.rst:155 msgid "Time units accounted in the current activity" msgstr "" -#: ../manage/time-accounting.rst:155 +#: ../manage/time-accounting.rst:156 msgid "Activity type (if enabled)" msgstr "" -#: ../manage/time-accounting.rst:156 -#: ../manage/time-accounting.rst:170 +#: ../manage/time-accounting.rst:157 +#: ../manage/time-accounting.rst:171 #: ../manage/webhook/log.rst:34 msgid "Created at" msgstr "" -#: ../manage/time-accounting.rst:171 +#: ../manage/time-accounting.rst:172 #: ../misc/object-conditions/basics.rst:25 #: ../misc/object-conditions/basics.rst:91 #: ../misc/object-conditions/basics.rst:113 @@ -9346,32 +9359,32 @@ msgstr "" msgid "Ticket" msgstr "" -#: ../manage/time-accounting.rst:159 +#: ../manage/time-accounting.rst:160 msgid "This filter contains all relevant tickets from the selected month." msgstr "" -#: ../manage/time-accounting.rst:167 +#: ../manage/time-accounting.rst:168 msgid "Agent currently assigned (ticket owner)" msgstr "" -#: ../manage/time-accounting.rst:168 -#: ../manage/time-accounting.rst:182 +#: ../manage/time-accounting.rst:169 +#: ../manage/time-accounting.rst:183 msgid "Time units accounted in the current month" msgstr "" -#: ../manage/time-accounting.rst:169 +#: ../manage/time-accounting.rst:170 msgid "Time units total (time accounted during ticket life)" msgstr "" -#: ../manage/time-accounting.rst:171 +#: ../manage/time-accounting.rst:172 msgid "Closed at (if applicable)" msgstr "" -#: ../manage/time-accounting.rst:174 +#: ../manage/time-accounting.rst:175 msgid "This provides you a per user filter on accounted time units. Each user has a total of time accounted in the current month (over all applicable tickets)." msgstr "" -#: ../manage/time-accounting.rst:190 +#: ../manage/time-accounting.rst:191 #: ../misc/object-conditions/basics.rst:27 #: ../misc/object-conditions/basics.rst:102 #: ../misc/object-conditions/basics.rst:133 @@ -9379,11 +9392,11 @@ msgstr "" msgid "Organization" msgstr "" -#: ../manage/time-accounting.rst:185 +#: ../manage/time-accounting.rst:186 msgid "This provides a list of all organizations where customers have caused accounted time in that month." msgstr "" -#: ../manage/time-accounting.rst:188 +#: ../manage/time-accounting.rst:189 msgid "You can also see entries for customers that are part of a primary organization. Users without an organization can be found in the Customer filter." msgstr "" @@ -9391,7 +9404,7 @@ msgstr "" msgid "Time accounting view with time accounted filters" msgstr "" -#: ../manage/time-accounting.rst:196 +#: ../manage/time-accounting.rst:197 msgid "Each heading allows you to download the CSV versions of the provided view via the download button next to it." msgstr "" @@ -9909,34 +9922,38 @@ msgid "Wish you could add your own fields to the New/Edit User dialog?" msgstr "" #: ../manage/users/index.rst:126 -msgid "Disabling this flag is a soft alternative to deleting a user. So what's the difference?" +msgid "Inactive users aren't able to login anymore. However, they can still be used in different places in Zammad (e.g. as ticket customer, in conditions in triggers and schedulers)." msgstr "" -#: ../manage/users/index.rst:129 -msgid "There is no way to restore a deleted user; inactive users can be reactivated at any time." +#: ../manage/users/index.rst:130 +msgid "What's the difference between deactivating and deleting a user?" msgstr "" #: ../manage/users/index.rst:132 -msgid "When a user is deleted, all their associated tickets are lost, as well; deactivating a user keeps all associated tickets intact." +msgid "There is no way to restore a deleted user; inactive users can be reactivated at any time." msgstr "" #: ../manage/users/index.rst:135 -msgid "Inactive users still appear in search results:" +msgid "When a user is deleted, all their associated tickets are lost, as well; deactivating a user keeps all associated tickets intact." +msgstr "" + +#: ../manage/users/index.rst:138 +msgid "Inactive users still appear in search results and can be used as a ticket customer:" msgstr "" #: ../manage/users/index.rst:0 msgid "An inactive user displayed in a customer search list" msgstr "" -#: ../manage/users/index.rst:141 +#: ../manage/users/index.rst:145 msgid "A slashed-out 👤 icon indicates an inactive user. In other cases, inactive users are grayed out." msgstr "" -#: ../manage/users/index.rst:147 +#: ../manage/users/index.rst:151 msgid "The :doc:`/manage/roles/index` define what users can do in the system. If you need to grant someone privileges to edit the knowledge base or access part of the admin panel, roles are the answer." msgstr "" -#: ../manage/users/index.rst:152 +#: ../manage/users/index.rst:156 msgid "The :doc:`/manage/groups/access-levels` define which tickets an agent can work with. If an agent is not receiving notifications for incoming tickets or can't be assigned to a ticket, you should have a look on the group permissions. Please note that the visibility of the group permission table depends on the role selection. It only shows up, if the selected role has the ``ticket.agent`` permission and when there is more than one active group in the system." msgstr "" @@ -9944,7 +9961,7 @@ msgstr "" msgid "Permissions in the edit user dialog" msgstr "" -#: ../manage/users/index.rst:167 +#: ../manage/users/index.rst:171 msgid "**Top:** User's roles decide what kind of actions they can perform and which :doc:`groups ` they belong to. **Bottom:** Group assignments can alternately be set on a per-user basis." msgstr "" diff --git a/manage/groups/settings.rst b/manage/groups/settings.rst index 2542223e..2785f857 100644 --- a/manage/groups/settings.rst +++ b/manage/groups/settings.rst @@ -9,6 +9,8 @@ Click on a group to edit it, or click on *New group* to create a new group. No matter if you're going to edit or create a new group, each group comes with the following settings you can adjust as needed. +Please note that groups cannot be removed. + Name This is the name your agents (and customers when using :doc:`/channels/web`) will see within the Zammad-UI. @@ -99,14 +101,19 @@ Note access the group management area. Active - Don't need the group any more? If you can't or don't want to recycle (rename) - the group, you can also set it to inactive. Agents and customers will no - longer be able to see the group and thus can't add, update or read it's - tickets. + Don't need the group anymore? If you can't or don't want to recycle (rename) + the group, you can also set it to inactive. Agents will no longer be able to + see or edit tickets in this group. However, customers can still interact + with their existing tickets in an inactive group. + + .. tip:: - .. note:: + Want to handle tickets from an inactive group, which are updated by + customers? - Currently, groups cannot be removed. + You could e.g. create a trigger which moves them to another + group when they got updated. Create this trigger before deactivating the + group so it is selectable in the trigger configuration. .. warning:: diff --git a/manage/roles/index.rst b/manage/roles/index.rst index dcff820b..ed67823b 100644 --- a/manage/roles/index.rst +++ b/manage/roles/index.rst @@ -121,3 +121,9 @@ Default at Signup of the **Manage > Roles** admin panel. .. warning:: 🙅 **Default roles should never provide admin/agent permissions.** + +Active + Roles can't be deleted but set to inactive. If you do so, all users loose + the permissions of this role. If this inactive role is the only one of a + user, this account isn't able to do anything in Zammad. The login is still + possible. \ No newline at end of file diff --git a/manage/time-accounting.rst b/manage/time-accounting.rst index 2d229dc5..9907b4a7 100644 --- a/manage/time-accounting.rst +++ b/manage/time-accounting.rst @@ -94,7 +94,8 @@ entry in the **Activity** table under the **Accounted Time** tab. You can manage available activity types in this screen like any other Zammad object. Only active types will be available for the selection when recording new -times. +times. If an activity type has accounted time, it is still displayed in tickets +and included in the accounted time overview. .. figure:: /images/manage/time-accounting/time-accounting-new-type.png :align: center diff --git a/manage/users/index.rst b/manage/users/index.rst index 67f652f0..dbf8c744 100644 --- a/manage/users/index.rst +++ b/manage/users/index.rst @@ -123,8 +123,11 @@ The ones that aren't are described below. You can! To learn more, see :doc:`/system/objects`. ▶️ Active - Disabling this flag is a soft alternative to deleting a user. - So what's the difference? + Inactive users aren't able to login anymore. However, they can still be used + in different places in Zammad (e.g. as ticket customer, in conditions in + triggers and schedulers). + + What's the difference between deactivating and deleting a user? 1. There is no way to restore a deleted user; inactive users can be reactivated at any time. @@ -132,7 +135,8 @@ The ones that aren't are described below. 2. When a user is deleted, all their associated tickets are lost, as well; deactivating a user keeps all associated tickets intact. - 3. Inactive users still appear in search results: + 3. Inactive users still appear in search results and can be used as a + ticket customer: .. figure:: /images/manage/users/customer-search-returns-inactive-user.png :alt: An inactive user displayed in a customer search list